[go: up one dir, main page]
Skip to content

Review remote_development route definitions, rewrite to eliminate unused routes

MR: Pending

Description

The following discussion from !125331 (merged) should be addressed:

  • @cwoolley-gitlab started a discussion:

    issue (non-blocking) We should revisit these route definitions, so that they only expose what we actually need.

    Currently, what we have here adds several routes that we don't use. Here's the output of bin/rails routes:

                                               remote_development_workspace_workspaces GET                   /-/remote_development/workspaces(/*vueroute)/:workspace_id/workspaces(.:format)                                                          remote_development/workspaces#index
                                        new_remote_development_workspace_workspace GET                   /-/remote_development/workspaces(/*vueroute)/:workspace_id/workspaces/new(.:format)                                                      remote_development/workspaces#index
                                                     remote_development_workspaces GET                   /-/remote_development/workspaces(/*vueroute)(.:format)                                                                                   remote_development/workspaces#index
                                                                                   POST                  /-/remote_development/workspaces(/*vueroute)(.:format)                                                                                   remote_development/workspaces#create
                                                  new_remote_development_workspace GET                   /-/remote_development/workspaces(/*vueroute)/new(.:format)                                                                               remote_development/workspaces#new
                                                 edit_remote_development_workspace GET                   /-/remote_development/workspaces(/*vueroute)/:id/edit(.:format)                                                                          remote_development/workspaces#edit
                                                      remote_development_workspace GET                   /-/remote_development/workspaces(/*vueroute)/:id(.:format)                                                                               remote_development/workspaces#show
                                                                                   PATCH                 /-/remote_development/workspaces(/*vueroute)/:id(.:format)                                                                               remote_development/workspaces#update
                                                                                   PUT                   /-/remote_development/workspaces(/*vueroute)/:id(.:format)                                                                               remote_development/workspaces#update
                                                                                   DELETE                /-/remote_development/workspaces(/*vueroute)/:id(.:format)                                                                               remote_development/workspaces#destroy

    Let's create a follow-up backend issue to address cleaning this up.

Acceptance Criteria

TODO: Fill out (required)

  • [Describe what must be achieved to complete this issue.]
  • [Describe another requirement needed to complete this issue.]
  • [Add additional acceptance criteria as needed.]

Technical Requirements

TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.]

Design Requirements

TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.]

Impact Assessment

TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]

User Story

TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]