#4716. Fixed issues with map details and thumbnail creation in home page #4726
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
Removed unnecessary and remaining double encoding due to the new API entry (PUT with Body, instead of URL encoded value, see #4673).
These caused an effective double encoding of the real respources (previously one encoding was removed by decoding by geostore, but the new API use a JSON as body, so no encoding is necessary anymore) and this made impossible to decode on a second load (only one decodeURIComponent is present, for retro-compatibility, but URLs was encoded 2 times in error.)
NOTE: didn't add unit tests because these where not covered and this part will be replaced soon with the Resource Observable. (see #2908)
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#4716 comment (thumbnails and details created in home page for maps are not available anymore after refresh)
What is the new behavior?
Thumb and detail card URLs are saved correctly (no double encoding anymore). Decoding is still present for retro-compatibility.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information