Use folder.active flag (set to false) to mark a folder as archived. When a folder is archivet, records of its descandants should be omitted from list_folder endpoint.
The inactive folder itself should be visible (with active: false) and filtered out in the frontend by default, but with an option to show archived folders as well.
Upon re-activation, the folder and its descendants should be included in the list_folder endpoint again.
This approach allows for a simple way to manage archived folders without permanently deleting them, reducing folder_list response size without needing to implement recursive filtering and/or recursive deactivation.
This approach only applies to folder_list endpoint, which is how the frontend retrieves folders. GraphQL queries won't be affected by this change and filtering by active: false will still return only explicitly deactivated folders.
Use folder.active flag (set to false) to mark a folder as archived. When a folder is archivet, records of its descandants should be omitted from list_folder endpoint.
The inactive folder itself should be visible (with active: false) and filtered out in the frontend by default, but with an option to show archived folders as well.
Upon re-activation, the folder and its descendants should be included in the list_folder endpoint again.
This approach allows for a simple way to manage archived folders without permanently deleting them, reducing folder_list response size without needing to implement recursive filtering and/or recursive deactivation.
This approach only applies to folder_list endpoint, which is how the frontend retrieves folders. GraphQL queries won't be affected by this change and filtering by active: false will still return only explicitly deactivated folders.