On Mon, Jun 17, 2013 at 02:53:31PM +0200, Pierre-Yves Chibon wrote:
On Mon, 2013-06-17 at 14:44 +0200, Miroslav Suchý wrote:
On 06/17/2013 10:59 AM, Pierre-Yves Chibon wrote:
That's also an option :) But I would argue for using "view" rather than "details".
Then we would have: /coprs/view/<user>/ /coprs/edit/<user>/ # edit the user info (if/when we have one) /coprs/delete/<user>/ # delete the user entirely
/coprs/new/<user>/ # create a new repo for this user /coprs/view/<user>/<repo>/ # view this repo /coprs/edit/<user>/<repo>/ # edit this repo /coprs/delete/<user>/<repo>/ # delete this repo
But then you can not go back in terms of url. I.e. by deleting trailing part of url you could not go back (which was your original problem).
From view you can but indeed from an edit page you cannot go back to the
view.
I guess having the action at the end might be the easiest then: /coprs/<user>/ /coprs/<user>/edit/ # edit the user info (if/when we have one) /coprs/<user>/delete/ # delete the user entirely
/coprs/<user>/new/ # create a new repo for this user /coprs/<user>/<repo>/ # view this repo /coprs/<user>/<repo>/edit/ # edit this repo /coprs/<user>/<repo>/delete/ # delete this repo
I am still interested in this and still willing to implement it. So what do you think of this proposal?
If we agree, shall I commit or shall I just send pull-request/patches to the list for review first (as this will change a number of files)?
Best regards, Pierre