Skip to content

PB-315: Handle legacy embed view #702

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

Merged
merged 2 commits into from
Mar 14, 2024
Merged

PB-315: Handle legacy embed view #702

merged 2 commits into from
Mar 14, 2024

Conversation

ltshb
Copy link
Contributor

@ltshb ltshb commented Mar 13, 2024

The legacy embed view was at hostname/embed.html. Unfortunately we cannot reroute
here to another path before the #, because the vue router using the createWebHashHistory
can only handle route after the hash. Therefore we have an external redirect
service that will redirect to /embed.html to ?legacyEmbed.

We use this pseudo legacyEmbed to redirect to #/embed once the other legacy
parameters have been translated.

NOTE: I first tried to set the redirect service directly to #/embed but then it made the startup procedure difficult as we needed to detect if other legacy parameters had to be translated and wait on them first. So for simplicity we use a legacy parameter as redirect
which simplify a lot the startup procedure which is then identical for other legacy parameters.

Test link

@ltshb ltshb requested review from pakb and ismailsunni March 13, 2024 11:07
Copy link

cypress bot commented Mar 13, 2024

Passing run #1108 ↗︎

0 172 22 0 Flakiness 0

Details:

PB-315: Handle legacy embed view
Project: web-mapviewer Commit: 12367078f2
Status: Passed Duration: 05:13 💡
Started: Mar 14, 2024 8:44 AM Ended: Mar 14, 2024 8:49 AM

Review all test suite changes for PR #702 ↗︎

Copy link
Contributor

@pakb pakb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the redirect service has already been updated with this new rule?

@@ -52,12 +47,12 @@ const appLoadingManagementRouterPlugin = (router, store) => {
isLegacyUrl,
...dispatcher,
})
unRegisterRouterHook()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What made it not working well keeping it under in the store subsribe?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing i just thought it would be wise to stop this plug-in sooner rather than later

ltshb added 2 commits March 14, 2024 09:41
The legacy embed view was at hostname/embed.html. Unfortunately we cannot reroute
here to another path before the #, because the vue router using the createWebHashHistory
can only handle route after the hash. Therefore we have an external redirect
service  that will redirect to /embed.html to ?legacyEmbed.

We use this pseudo legacyEmbed to redirect to #/embed once the other legacy
parameters have been translated.
@ltshb ltshb force-pushed the feat-PB-315-legacy-embed branch from d2bdcbd to 1236707 Compare March 14, 2024 08:41
@ltshb
Copy link
Contributor Author

ltshb commented Mar 14, 2024

@pakb yes the redirect is ready and applied on dev see https://github.com/geoadmin/infra-kubernetes/pull/508 with this pr merge I’ll do some test before closing the ticket.

@ltshb ltshb merged commit 73874f8 into develop Mar 14, 2024
@ltshb ltshb deleted the feat-PB-315-legacy-embed branch March 14, 2024 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants