Consider refactoring api_field_names to API entity

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The following discussion from !81564 (merged) should be addressed:

• @.luke started a discussion:

  Thought (not blocking)

  This method in Integration is so specific to the API (named as such!) that I wonder should just be a private method in the API-related code, perhaps the entity.

This is valid - this method doesn't really belong on the model. We should rely on field metadata to avoid any need to override this.