Wondering if there’s any possibility to have a versioning for those components.
Case scenarios:
- Being able to undo a Module, Page or Workflow to a previous state easily.
- Share those differentials from version to version via export.
2 Likes
Hi
I trust you are well.
I believe these features would be great suggestions and some have already been ‘aired’ internally.
If you would like to make any formal suggestions, please feel free to do so on our GitHub repo with as many details as possible, and we will review this for potential features.
Kind regards
1 Like
Versioning of Modules, Pages and Charts and Workflows and also Namespace as a whole would be extremely necessary and useful.
Is this being considered? Which version of Corteza it is planned in?
I am not talking about code level versioning for developers, but Object level at a higher level for no-code users.
1 Like
We know; it was tossed around plenty of times but we never fully decided when it would be developed and what version it’d be included in
2 Likes