Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging to file #615

Closed
5 tasks done
ptvrajsk opened this issue Mar 1, 2021 · 1 comment · Fixed by #616
Closed
5 tasks done

Logging to file #615

ptvrajsk opened this issue Mar 1, 2021 · 1 comment · Fixed by #616
Labels
category.Feature a new feature p.Medium to be done when there are no other higher priority issues

Comments

@ptvrajsk
Copy link
Contributor

ptvrajsk commented Mar 1, 2021

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

    • 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...)

We can solve this issue with the following steps.

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)

  • 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.
@ptvrajsk ptvrajsk added category.Feature a new feature p.Medium to be done when there are no other higher priority issues labels Mar 1, 2021
@ptvrajsk
Copy link
Contributor Author

ptvrajsk commented Mar 2, 2021

@CATcher-org/2021-devs @anubh-v

Should the button to download the log be left on the HeaderComponent? Or do you guys have any suggestions on where we can place it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category.Feature a new feature p.Medium to be done when there are no other higher priority issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant