Change Details

Preamble: this is abonineably trivial and stupid and super-corner case. Scenario: * Create Project "Awesome App Developers" * use that group for years * Today, create Sub-project {nav Awesome App Developers > Sub-project Yeah} What happens: The "Awesome App" project has members that cannot be edited anymore in any way. The user interface suggests to edit its sub-Project, but there aren't. Current workaround 1: Create a dummy sub-project, change members from there. Current workaround 2: ``` $ mysql phabricator_project UPDATE project SET hasSubprojects = 0 WHERE id = <awesome app id>; ``` Proposal: If a CLI administrator deletes the "Sub-project Yeah" from command line with the lovely workflow `./bin/remove destroy`, Phorge should probably restore its parent project as such, so, restoring `project.hasSubprojects` if that is semantically true again.

Preamble: this is abonineably trivial and stupid and super-corner case. Scenario: * Create Project "Awesome App Developers" * use that group for years * Today, create Sub-project {nav Awesome App Developers > Sub-project Yeah} * Delete "Sub-project Yeah" What happens: The "Awesome App" project has members that cannot be edited anymore in any non-creative way. The user interface suggests to edit its sub-Project, but there aren't. Current workaround 1: Create a dummy sub-project, change members from there. Current workaround 2: ``` $ mysql phabricator_project UPDATE project SET hasSubprojects = 0 WHERE id = <awesome app id>; ``` Proposal: If a CLI administrator deletes the "Sub-project Yeah" from command line with the lovely workflow `./bin/remove destroy`, Phorge should probably restore its parent project as such, so, restoring `project.hasSubprojects` if that is semantically true again.

Preamble: this is abonineably trivial and stupid and super-corner case. Scenario: * Create Project "Awesome App Developers" * use that group for years * Today, create Sub-project {nav Awesome App Developers > Sub-project Yeah} * Delete "Sub-project Yeah" What happens: The "Awesome App" project has members that cannot be edited anymore in any non-creative way. The user interface suggests to edit its sub-Project, but there aren't. Current workaround 1: Create a dummy sub-project, change members from there. Current workaround 2: ``` $ mysql phabricator_project UPDATE project SET hasSubprojects = 0 WHERE id = <awesome app id>; ``` Proposal: If a CLI administrator deletes the "Sub-project Yeah" from command line with the lovely workflow `./bin/remove destroy`, Phorge should probably restore its parent project as such, so, restoring `project.hasSubprojects` if that is semantically true again.