feat(catalog): Forced metadata#1077
Merged
PhilippeLafreniere18 merged 26 commits intonextfrom Jun 22, 2022
Merged
Conversation
PhilippeLafreniere18
approved these changes
Jun 21, 2022
PhilippeLafreniere18
approved these changes
Jun 22, 2022
5 tasks
cbourget
pushed a commit
that referenced
this pull request
Mar 21, 2023
* Metadata sur services externes, aucune réponse - à vérifier * fix last commit * draft forcedMetadataUrl * draft forced metadata url * fix draft commit forced metadata url * draft forced NewMetadataURL * fix last commit * draft backup * force a new metadata URL or Abstract, 1 per link, not layer * tests change single layer + other layers * final version with some overrides to fix * lint * refactor and minor code fix * minor fix * rename forced metadata properties, updated examples * change All for * * change All for * * change all for * * refactor(catalog): forced properties refactor * lint Co-authored-by: mneige <90412486+mneige@users.noreply.github.com> Co-authored-by: Philippe Lafreniere <philippe.lafreniere@msp.gouv.qc.ca> Co-authored-by: Pierre-Étienne Lord <pe_lord@yahoo.ca>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Please check if the PR fulfills these requirements
What is the current behavior? (You can also link to an open issue here)
When we integrate external layers in a composite catalog, the content of the "metadata" button is automatically generated from the layer, when the information is set. It is not possible to change it as we can using mapfiles.
What is the new behavior?
It is now possible to force the "abstract" (a text), newMetadataAbstract, or the "metadataUrl" (a link), newMetadataUrl, as the content of the "metadata" button of a layer in a composite catalog. It is possible to force it for a single layer, using its layer name, or to all layers (newMetadataUrlAll, newMetadataAbstractAll) of a link. If we set newMetadataAbstractAll or newMetadataUrlAll, even single layers will be overridden.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications:
Other information: