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

Rethink routing of projects/organizations

未关闭
#1,570 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
needs clarification
主要语言
JavaScript
星标
120
派生
75
PR 合并指标
30 天内没有已合并 PR

描述

# 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.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。