Lets open some issue, e.g.:
https://pagure.io/pagure/issue/2222
By deleting the issue number I got this url:
https://pagure.io/pagure/issue/
And I expect this gets me to the list of issues. But it wont, I just got '404'. This is very surprising and it prevents me from using Advanced Locationbar [1] for Pagure navigation.
Actually, I can't remember any other site where this would not work and I think that the "issues" url should be always plural, e.g.:
https://pagure.io/pagure/issues/2222
This is convention for most web frameworks I know ...
BTW I suspect that the #2222 might be somehow related to this?
Given the impact this would have to change this now, I think I am more favourable to make a redirect from https://pagure.io/pagure/issue/ to https://pagure.io/pagure/issues/
Would that work for you?
Metadata Update from @pingou: - Issue tagged with: RFE
It would probably work for my case.
However, wouldn't it be better to make the "issues" new default and just redirect the "issue" for backward compatibility? This would allow to phase out the "issue" endpoint one day ....
Hm, I guess we could also look into this but it would be quite a bigger change as we would likely have to adjust the API endpoints as well to keep things coherent. In a way I kinda like the singular /issue/ but I can see how that's not a standard, so I can be convinced into changing this.
/issue/
@cverna @puiterwijk @vivekanand1101 @farhaan any opinion on this?
It should be issues but i think people must have used absolute urls instead of # ones. We can add redirect to two views(for UI and another two for API). For listing all the issues and for each individual issue. This way people will start using the issues/1234, since they will be redirected to this and not issue/1234. And later on, if you feel it should removed, it won't remain a big deal.
issues
issues/1234
issue/1234
We can also do this in two steps: Add only redirects for issues and later on issues/1234
Also, we will have to do this for PRs views as well :/
Metadata Update from @wombelix: - Issue set to the milestone: 6.0