Geo Replicable - Rename Nodes to Sites
What does this MR do and why?
This change is MR 4 of 5 for #393925 (closed)
Geo has rebranded the term Nodes
=> Sites
. We have taken the Facade-first approach to rename only customer facing content while leaving all the technical content like file names, method names, variable names.
Now that the rebrand is mature and we are sure the term Sites
is here to stay we are aiming to complete the rename for the technical side of things too.
Focus of this MR
This MR is focused on renaming the FE code that is inside of the geo_replicable
scope. This includes all file names, the folder itself, and all component internals.
Screenshots or screen recordings
No change or console errors
Geo Replicable List View |
---|
Find in files results
geo_replicable/ | spec/geo_replicable/ |
---|---|
notes about find results:
- in
geo_replicable/
-
index.js
=> Multi Version Support, will be removed in #396730 (closed) -
utils.js
=>node_proxy
renamed tosites_proxy
in #396741 -
replicable_type_query_builder.js
=>Query.geoNode
renamed toQuery.geoSite
in #396739 -
actions.js
=>Query.geoNode
renamed toQuery.geoSite
in #396739
-
- in
spec/geo_replicable/
How to set up and validate locally
- Fetch and checkout this branch
- Setup Geo (How to setup Geo)
- Access your Secondary GDK UI
- Navigate to Geo Dashboard (
/admin/geo/sites
) - Scroll down to the Secondary Site
- Click one of the links in the Replication Details section (ie. Package Files)
- Ensure the list and any pagination works with no console errors
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.