Option to read asset layers from configuration. #4119
Merged
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 adds the option to read asset layer configuration from the configuration file, instead of in the JavaScript. This will make the config file quite a bit bigger (but could include it from another file, I imagine), but should make it a bit easier to add or change asset layers without having to update the code. Also a step towards making it configurable elsewhere in future. I've done Lincolnshire in this PR as a starting example, you'd need the config given below in order to have all the same layers that were present in the JS. This won't (yet) handle every layer, but should handle all standard ones.