[data]: Data Preparation for Improved Data Model #738
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Relequestual
requested changes
Jun 10, 2024
There was a problem hiding this comment.
I don't think it makes sense to have empty arrays as values.
Where there's no values in an array, let's simply ommit the key.
I appreciate that doing so may have enabled you to more quickly create the data.
Values which can be empty should not be required.
In fact, it may be preferable to not allow empty arrays in the data to avoid possible errors in creating or modifying the data.
Relequestual
approved these changes
Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
This PR aims to improve the current data model for the website to enhance maintainability, completeness, and structure. The existing model primarily contains validators' data for the tooling section, while other data is hardcoded into the markdown files. This PR cleans unused and outdated fields, redesign the data model to consolidate all relevant data into a single file, and add maintainer details for future community events.
Issue Number:
Screenshots/videos:
If relevant, did you update the documentation?
Summary
Does this PR introduce a breaking change?