Skip to content

Geo Sites - Rename geo_sites_form

Zack Cuddy requested to merge 393925_03-geo-sites-geo_node_form-rename into master

What does this MR do and why?

This change is MR 3 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_node_form scope. This includes all file names, the folder itself, and all component internals.

Screenshots or screen recordings

No change or console errors

New Site Edit Site
Screenshot_2023-03-10_at_1.30.34_PM Screenshot_2023-03-10_at_1.31.07_PM

Find in files results

geo_site_form/ spec/geo_site_form/
Screenshot_2023-03-10_at_3.37.31_PM Screenshot_2023-03-10_at_1.40.49_PM

notes about find results:

  1. in geo_site_form/ the only result has comment explaining why (related to gitlab.rb)

How to set up and validate locally

  1. Fetch and checkout this branch
  2. Setup Geo (How to setup Geo)
  3. Access your Primary GDK UI
  4. Navigate to Geo Dashboard (/admin/geo/sites)
  5. Click Add site button
  6. Ensure form, links, and submitting work
  7. Click Edit on new site you created above
  8. Ensure form, links, and submitting work

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Zack Cuddy

Merge request reports