MG-22 - Update Metadata formatting #30
Merged
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
dborovcanin
changed the title
ianmuchyri
force-pushed
the
22-metadata
branch
2 times, most recently
from
1ebb96f
to
b6aeff3
Compare
implements code mirror which creates a code editor that allows proper inputting of metadata in json tree format Signed-off-by: ianmuchyri <[email protected]>
ianmuchyri
force-pushed
the
22-metadata
branch
from
14c573c
to
c6e0269
Compare
dborovcanin
requested changes
Dec 21, 2023
Signed-off-by: ianmuchyri <[email protected]>
dborovcanin
approved these changes
Dec 21, 2023
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 type of PR is this?
What does this do?
Add the feature of inputting metadata in JSON formatting by employing a code editor. All metadata inputs act as code editors allowing a user to input metadata in JSON tree format
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Did you document any new/modified functionality?
Notes