Fix: Refresh concepts page on jump to

[Bilelkihal]

Issues fixed:
#860
#845

Changes

• Replace reloading the page using Turbo.visit when performing a jump_to, by reloading the whole page (fb06a1a)

[Bilelkihal]

✅

[Bilelkihal]

@syphax-bouazzouni Deployed to stage you can test it there

[syphax-bouazzouni]

Even though this is a simple solution for most issues, it is not acceptable because the UX is worse compared to what we had before. For example, see this remark: GitHub Issue #359.

The desired solution for these types of issues is based on the concept of idempotence, which ensures that running the same JavaScript code multiple times does not break the application.

Why your solution works:

• Turbolinks.visit does not refresh the entire page but only replaces the body. This means the old JavaScript context remains active, and when the new body is rendered, the same JavaScript code is executed again, potentially causing conflicts with the existing code.
• On the other hand, using window.location fully reloads the page, clearing the old JavaScript context and starting with a fresh state, which resolves the issue.

The proper solution is to fix our JavaScript code to handle idempotency. This means checking if the code has already been initialized before running it again to avoid conflicts.

Here is an example of issues using Turbo.visit in bioportal ncbo#345, fixed like this https://github.com/ncbo/bioportal_web_ui/blob/sync-agroportal/app/javascript/controllers/container_splitter_controller.js

[syphax-bouazzouni]

Close as the solution was not accepted, @Bilelkihal will open a new PR once working on it again.