when a developer want to maximise the entities that are returned by a SOQL they need to try various from entities to see which includes the most entities.
When extracting the from options from the persisted JSON, the "entities" pure fn could return objects instead of strings. Those objects can contain the "from" entity name and also a label with (n) appended. N would be the count of entities included when that entity is used as the from for a SOQL query.
This makes it easy for the user to know which entity has the greatest reach without needing any new UI components i.e. keeping UI clean
when a developer want to maximise the entities that are returned by a SOQL they need to try various from entities to see which includes the most entities.
When extracting the from options from the persisted JSON, the "entities" pure fn could return objects instead of strings. Those objects can contain the "from" entity name and also a label with (n) appended. N would be the count of entities included when that entity is used as the from for a SOQL query.
This makes it easy for the user to know which entity has the greatest reach without needing any new UI components i.e. keeping UI clean