Geo - Remove temporary multiversion support
What does this MR do and why?
Closes #396730 (closed)
Cleans up technical debt intentionally introduced in #393925 (closed)
This MR is a result of my misunderstanding of Backwards Compatibility in JavaScript.
The short explanation is that I had thought when updating the link between HAML / JS (ie. Data Attributes), we would need the Frontend Bundle to support the possibility of the FE bundle deploying before the BE bundle which would cause a disconnect between the two files where the BE referenced the old code (ie. old Data Attributes) and the FE referenced the new code.
To solve this, I felt temporarily having the FE support both HAML file possibilities seems straight forward.
Long Explanation: !113771 (comment 1305435081)
As it turns out this was not needed at all but it didn't hurt anything. This MR is simply removing that duplication as it is and was not needed.
Screenshots or screen recordings
No visual changes
How to set up and validate locally
- Fetch and checkout this branch
- Setup Geo (How to setup Geo)
- Access your GDKs
- Navigate around the Geo Application (
admin/geo) - Ensure everything still works
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #396730 (closed)