code-corps / code-corps/code-corps-ember

Rethink routing of projects/organizations

Ouverte
#1,570 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
needs clarification
Langage dominant
JavaScript
Étoiles
120
Forks
75
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

# Problem

Per @begedin in a PR:

> The current layout of /:slug/projects is strange and seems to be lacking. On the other hand `/organizations/:slug` seems the way to go.
>
> The thing is, having both seems a bit redundant. Is there any specific reasoning to have two, or did it just somehow happen along the way.
>
> Merging the "good" behavior from both places into a single namespace under /`:organization_slug` seems like the way to go.
>
> It also looks like we started off with `/:slugged_route_slug` with the impression of users being able to have projects at some point to. Is that still a goal? If not, I think we could rewrite our router and organize our files in a clearer, more understandable way, but it would involve a lot of changed files to do so.

This needs some discussion.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.