Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define self reporting tooling data structure #13

Closed
Relequestual opened this issue Jun 6, 2024 · 0 comments · Fixed by #12
Closed

Define self reporting tooling data structure #13

Relequestual opened this issue Jun 6, 2024 · 0 comments · Fixed by #12
Assignees
Labels
Status: In progress This issue is being worked on, and has someone assigned.

Comments

@Relequestual
Copy link
Member

There's a good number of tools in the JSON Schema ecosystem. We often get requests to add new tools or update their indicated support or other details.

In order to avoid such updates, defining a data structure for tooling to self report their existance, support, and details, seems like a good idea.

We would need to define the data structure required, and then look for and pull in the data into a single file.

The expectation is that this is only for open source tooling hosted on GitHub. We can look at supporting GitLab and possibly others at a later point in time.

Tis is related to json-schema-org/community#412

Once collected, data can be utilised to augment the JSON Schema website tooling page data, and the JSON Schema Landscape diagram.

Both the website and the landscape repository house their own data at current. It is expected that a transition to the data in this repository would eventually be the single source of truth, but that may take some time. While that is not the case, this data will augment the data in those repositories as is feasable.

@Relequestual Relequestual added the Status: In progress This issue is being worked on, and has someone assigned. label Jun 6, 2024
@Relequestual Relequestual self-assigned this Jun 6, 2024
@Relequestual Relequestual linked a pull request Jun 6, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: In progress This issue is being worked on, and has someone assigned.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant