1866-BUG-Bad_feature_info_propagation_to_store #1868
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.
Description
Modifications to the feature-info-event-processor and the legends-layer-set files to resolve the propagation issue. The problem was that the queryable flag of a layer, if not set in the config file, was known only when the metadata were loaded. At that point in time, the registration of the queryable layers from the config file was done, but those relying on the metadata were never registered. A call to registerToLayerSets was added in the LegendsLayerSet instance to register those layers when the metadata are loded.
Fixes #1866
Type of change
How Has This Been Tested?
As usual, using the Chrome Devtools
Deploy URL: https://ychoquet.github.io/GeoView/all-layers.html
Checklist:
I have made corresponding changes to the documentationI have added tests that prove my fix is effective or that my feature worksNew and existing unit tests pass locally with my changesThis change is