feat(metadata): Require use-cases in meta json#4321
Merged
Conversation
Co-authored-by: Copilot <copilot@github.com>
ericfennis
changed the title
…quire-usecases-meta-json
This file contains hidden or 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
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.
Changes
Adds new property to meta json files names "use-cases".
Motivation
For each icons we already require to provide use-cases. But now these usecases are only documented in the PR descriptions.
We should also add these to the meta json files, to document them for the icons.
These usecases are usefull for information to improve context for LLMs to indicate the use for each icon, which (hopefully) contributes improves the DX when using AI coding tools.
This will be part of bigger project to enrich context for AI coding tools.