Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Release v1.31.0 - #minor #947

Merged
merged 19 commits into from
Jun 21, 2024
Merged

New Release v1.31.0 - #minor #947

merged 19 commits into from
Jun 21, 2024

Conversation

pakb
Copy link
Contributor

@pakb pakb commented Jun 21, 2024

pakb and others added 19 commits June 20, 2024 12:07
identify request already provides us with all what we need (feature data), the only thing missing is the HTML popup.

This means getFeature request is now only called when the app is loaded with pre-selected features.

This reduces the number of calls to our backend for an identify on the map (should be a bit faster)
they are required for some layer, as the result of these endpoints can vary depending on the map resolution.
…quests

PB-669 : separate html popup request from getFeature
looping on sub-layers and bunching together any fulfilled getFeatureInfo requests.
…_group_of_layers

PB-681 : add support for group of external layers getFeatureInfo
Try to make the code cleaner, more robust and easier to understand (not sure
I achieved this though).

One major changes is that for the "all" hack, now in the url we don't use anymore
@year=9999 but @year=all (legacy timestamp with 9999 are still working and are
translated to @year=all)

Also added support for @year=none when a layer as no data for timeslider
preview year.

I also tried to document the layer attributes and all special cases

I also created a ticket PB-680 to do more clean up concerning the "all" hack
in future.
Now the layer timestamp to use is always set to the layer config so there is
no need to look at the preview year of the time slider down the way. This
simplify the code.

Note the preview year is still used as URL param to create permalink with
timeslider activated at a particular year.
In legacy link no timestamp is an empty string which should result of using
the default layer timestamp, because in javavascript `&& ''` is true, the
previous code resulted in a @year=none
In this case we don't want to provide the time selector button
WMTS layer have almost always a timeConfig, but most of the time with a single
timestamp. In this case we don't want to have the @year attribute, same for
external layer that don't have ISO timestamp.
Also split a test into 2 it(), somehow it strangely failed when done in one
go while when manually testing it worked. I could not understand exactly why.
It seems its related to a timing issue with the dispatching of the @year
and timeSlider parameter.
Before when the timeSlider was active and we added a layer, the new layer did
not set its current year to the time slider year until the slider changed.

Also reduced the number of dispatch by only dispatching the set year to layer
that don't have yet the correct year.
@github-actions github-actions bot changed the title Release New Release v1.31.0 - #minor Jun 21, 2024
Copy link

cypress bot commented Jun 21, 2024

Passing run #2710 ↗︎

0 209 21 0 Flakiness 0

Details:

Merge pull request #942 from geoadmin/bug-PB-590-time-slider-no-data
Project: web-mapviewer Commit: e8aa05a24a
Status: Passed Duration: 03:49 💡
Started: Jun 21, 2024 9:07 AM Ended: Jun 21, 2024 9:11 AM

Review all test suite changes for PR #947 ↗︎

@pakb pakb requested review from ltshb, ltkum and schtibe June 21, 2024 09:16
@pakb pakb merged commit 8ee61f3 into master Jun 21, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants