Different workflow for exporting to code (panels and views)

I was having a discussion with sdboyer and some other Palantir folks about loss of Panel configuration due to some bad exported code. I had a thought, that I'd like to open up for discussion. What if when you exported code, it didn't replace the Panel (or view) in the database, but instead gave you an option to view the one now in code. You would then, by some mechanism, be able to toggle the 2 different displays: the database version of the panel, and the code version of that same panel. This would, for me, be a very nice feature for testing that the code version does work before I completely blow away my database version.

This discussion started because we recently found a bug in the exporter of some panels - and I have no way to get back to the original panel config without overwriting the database from a backup - which I cannot do at this point. I have the same concern when doing bulk exports on views.

I think it is good to know when a view or panel in the database is overridden b/c it also appears in code, but that you can verify that the code version works before removing the database one.