feat: Export process logging (M2-9624) - #2110
Merged
Merged
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
aweiland
approved these changes
Aug 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixorfeaturebranches intodeveloporreleasebranches viaSquash and Merge(to keep clean history)📝 Description
🔗 Jira Ticket M2-9264
This PR adds comprehensive error logging for the data export process, since currently, next to none is enabled.
The logging was put behind a manually-set session storage key. This can be enabled with:
🪤 Peer Testing
Once the logging has been enabled, exporting any data for either activities or full applets should display logs in the browser console
✏️ Notes
If logging is no longer required/desired, simply removing the same key from the session storage will disable it.