This fixes that behaviour where users will now see error checking activate when re-opening vscode and editing an ASL document from a previous session
Testing
I elected to keep the two new functions private as they only pertain to activation. Thus there are no unit tests with this particular change.
I verified this fix by opening up a new vscode session from which I had previously been editing an ASL document. I've attached a video for proof.
I wasn't sure if we can mock this behaviour somehow in integration tests or E2E tests so if anyone has any ideas or recommendations, I'm happy to implement them.
Problem
Users who open vscode after previously editing an ASL document are not seeing error checking activate
Solution
This fixes that behaviour where users will now see error checking activate when re-opening vscode and editing an ASL document from a previous session
Testing
I elected to keep the two new functions private as they only pertain to activation. Thus there are no unit tests with this particular change.
I verified this fix by opening up a new vscode session from which I had previously been editing an ASL document. I've attached a video for proof.
I wasn't sure if we can mock this behaviour somehow in integration tests or E2E tests so if anyone has any ideas or recommendations, I'm happy to implement them.
Demo
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.