Adding support for sub languages on the "backend" #158
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.
Description
Add the ability to parse sub languages to the snippet parser, and to consolidate them.
To consolidate them we save the json and svg with the following name format
language--subLanguage
.I didn't want to put them under folders as i think it would complexify things in the frontend.
Also, as we are using slugify to generate the
language
andsubLanguage
name, a--
can never occur outside of that usecase.As it stands we support only 1 level of nesting languages.
Some small changes also include renaming some names key to
name
(lang
in_index.json
andcategoryName
)Type of Change
Checklist
Related Issues
Related to #136