A code exporter is desired for these two reasons.
1 .Currently code backup functionality is almost non-existent. Backup via standard database backup is risky for the fear that code and data will be rolled back or forwarded simultaneously, which is not desirable sometimes.
2. Code change audit is frequently done in big teams, commonly with git, diff, and other external tools. Exported codes make this process more smooth.
Lingyan, thank you for your idea. InterSystems experts (see comments below) proposed alternative ways to implement the task you mentioned in your idea. That's why the status of the idea was changed to "Will not implement".
I'd better store all the code in a Git repository - and repositories have all the functionality for backup, maintaining the history, and analysis. Package manager ZPM helps to import code for development and deployment in a handy and robust way.
You can use the VS Code ObjectScript extension to facilitate this.