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.
This pull-request wants to simplify the definitions of aliases.
Here at ITK we use intensively aliases, with time our aliases.properties grownth exponentially. Lots of patterns are similare but with little changes.
So we have implemented a json parser, and we have added variable feature.
Specifications :
yoga_aliases
directory inressources
directory contains the definitions in multiple files ending by json$
for aliase and@
for variableExamples (from tests) :
from
to
Or from
to
And with variables :
Could be represented as :
More complex variables can be used.
The JSON files must be in
yoga_aliases
directory in the ressources directory.It can contain all files you want, the name of file is not used, but it needs to finish by .json.
We use a file, for a view in our application, and each file contains all requests aliases for this view.
A variable can be defined in one file and used in an other one. And a file can contain only aliases or only variables, it's as you want.
To resume :