You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should implement Logging capabilities to give further insights on errors that users may face.
Currently Client-Side JS Applications do not have access to disk so writing a local log-file is impossible. Alternatively these are some possible solutions to tackling logging.
Work-Arounds
Write to localStorage from Angular to cache information on the browser.
localStorage works as a key-value pair. So we can add data with a Log Key and verify SessionData before appending log information.
We can have a button added to the App where the user can download log information as a text file from the browser and send it to us for a review (in addition to screenshots, etc...)
Verifying Session Information (SessionID) prior to appending to log. [ We could keep the last 3/4 SessionLogs (We can discuss how many session infos would be prudent to keep)] (PR Implement cached logging capability #616)
Formatting Log file to allow for easier troubleshooting (There is a chance that the file may come out as 1 long string since we are just pulling it from memory and dumping into a text file) (PR Implement cached logging capability #616)
We may also want to add more log information around our codebase that documents user actions in the future so that our log files can be more detailed and we can have a clearer picture on the steps taken by users prior to a crash or issue.
Directly writing to repository file on each major action. (Submitting Issue / Deleting Issues / Editing Issues)
If we have both implemented we can verify the 'Local Actions' and what was registered by the Backend for troubleshooting but this might take more time to do.
The text was updated successfully, but these errors were encountered:
As discussed earlier,
We should implement Logging capabilities to give further insights on errors that users may face.
Currently Client-Side JS Applications do not have access to disk so writing a local log-file is impossible. Alternatively these are some possible solutions to tackling logging.
Work-Arounds
localStorage
from Angular to cache information on the browser.localStorage
works as a key-value pair. So we can add data with a Log Key and verify SessionData before appending log information.We can solve this issue with the following steps.
localStorage
mechanism (Enhancing our current LoggingService) (PR Implement cached logging capability #616)We may also want to add more log information around our codebase that documents user actions in the future so that our log files can be more detailed and we can have a clearer picture on the steps taken by users prior to a crash or issue.
Resources
2. - [ ] Write to individual repository (Bug-Reporting Phase / Tester-Response Phase)The text was updated successfully, but these errors were encountered: