Skip to content

Improve URL structure  #402

@WojcikMike

Description

@WojcikMike

Relates to:

There is a need to analyze and possibly modify the URL paths to the different failed message screens.

Previously our URL's looked as follows:

  • /failedMessages - failed messages screen
  • /failedMessages/{{id}} - one message screen

Becasue @WilliamBZA made a PR (#399) to provide deep linking groups he used "our" url path, so currently it looks like this:

  • /failedMessages - failed messages screen
  • /failedMessages/{{id}} - failed messages screen with a group of given id selected

Which means that we lacked URL for this feature. Now because on our page we show a bit more than only failed message (as it can also be archived message, or successful processed message) @WojcikMike decided to go with the following path for individual message URL paths in PR (#381):

  • /message/{{id}}

However, URLs often are segmented to mimic navigation. From this perspective, /failedMessages is parent of both groups and individual messages. So @sergioc argues that both children should be nested under the parent to mimic the nav structure. Also avoid using two words in "oneWord" to improve legibility of the URL, as well as caps. So use this structure in the end:

  • /failed-messages (default view) or alternative show directly /failed-messages/groups
  • /failed-messages/groups/{{group.id}}
  • /failed-messages/message/{{message.id}}

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions