olisb
commented
6 months ago This is smart, I like it. But perhaps the popularity count should only be based on live schemas (i.e. those in the production Index / main branch) otherwise the results could get skewed if someone uses a field in a test schema of which they create multiple versions
As the library repository grows with new schemas and fields, we want to make it easy to see:
The app will need to inventory all of the fields and schemas in the library repo (test and main branches) and generate the following views:
1) Field popularity - a table that list each standard field along with a count of the number of schemas it appears in. The number should present an expandable list that shows every schema that uses it.
2) Schema fields mapping - a table that shows each schema and every standard field that is used in it. A third column should list the custom fields embedded in each schema as well.
3) Field collisions - we want to know when schemas have embedded fields with the same name so as to rename them to avoid problems if they have different meanings. There should be a check to ensure they don't collide with fields in the standard fields directory either.