Carlos

> I don't see any change related to my remark concerning code duplication. It's in my to-do list

> I don't see any change related to my remark concerning code duplication. I have rewritten the form contents, so now it's a separated div: - visually groups the note...

> The commands should reflect the intention of the user and not be used as re-usable code. For example, the user intent it to change status or update issue in...

> Can it be merged or are you still discussing ? No merge yet. My questions are still open, regarding the command, but not blocking though. There is an UI...

> @cproensa any chance of finalizing this PR to merge it? Would like to, but at the moment i have little time, and it's complicated with the current situation.I guess...

I'm not familiar with the new Commands scenario, but does it really need a Command for something that does not make changes? Also, i have proposed #1480 that is making...

> @cproensa I haven't been doing it partially relying on SOAP API helper functions. However, I think it is a good practice to have a command for each REST API....

As another note: I am thinking that disabled projects should not be published. Form a user point of view, disabled projects don't exist and should not be operated upon. That's...

After working with the hierarchy refactor, iirc, the only places we are (currently) using any call that needs disabled projects are: - manage projects, pages and api commands - category...

@obmsch i think i see it clearer now with your comment. All those api routes in projects_rest.php were added as intended to project _administration_. In such case: If you want...