@analytics_union Thanks for the feedback! I love the idea of doing this
at the base resource level (rule, data element, extension). Do you think
it still makes sense to do this at code editor level even if we do it at
the base resource level?
We're thinking about the UX on this. I'd love any feedback y'all have.
Here's what I have so far...Save temporary code every time you stop
typing for more than 1 secondWhen coming back to the view after
unintentionally leaving, it will prompt you to restore your unsaved
codeIf you modify the code, save, or cancel we consider it intentional
code lock-in and throw away the old temporary saved codeTemporary code
is saved based on the current URL so it's different for every
viewQuestions...How long ...