We are getting a lot of warnings during tokens' generation mentioning name collisions.
I started looking into this and discovered the nested format idea, which works great for the formats where it's set up (and we had to add it to a few of our formats), but then I realized I was still getting errors during asset files generation with the json/format format.
Looking at the code + at its output, it seems like this format is a nested format too, but I am guessing it was missed during the time where nested formats where introduced.
So this PR is just making the json/format officially a nested format, so there won't be anymore wrong warnings for it.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #, if available:
Description of changes:
We are getting a lot of warnings during tokens' generation mentioning name collisions.
I started looking into this and discovered the
nestedformat idea, which works great for the formats where it's set up (and we had to add it to a few of our formats), but then I realized I was still getting errors during asset files generation with thejson/formatformat. Looking at the code + at its output, it seems like this format is a nested format too, but I am guessing it was missed during the time where nested formats where introduced.So this PR is just making the
json/formatofficially anestedformat, so there won't be anymore wrong warnings for it.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.