Persisting Login Session in Local Development #709
-
Hello, can I confirm that When it comes to local development, I find this a bit troublesome, since if I make changes to the codebase (especially to the HTML code which governs the UI), angular will automatically trigger a hot-reload. This will always cause the app to refresh and I'm always kicked out to the start-up page and I have to re-login again just to see the changes I've made. Is there any way to prevent having to re-login on every reload? Thanks in advance! 😄 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@AudreyFelicio I converted your issue into a discussion topic, mostly to test the new 'Discussions' feature of GitHub. |
Beta Was this translation helpful? Give feedback.
-
Thanks for raising the issue @AudreyFelicio. It is not possible to persist the login session, currently. This is an inconvenience, but I don't think we can implement this feature easily, as we would need another server-side process to store the user's access token when they are not using CATcher. |
Beta Was this translation helpful? Give feedback.
Thanks for raising the issue @AudreyFelicio. It is not possible to persist the login session, currently.
This is an inconvenience, but I don't think we can implement this feature easily, as we would need another server-side process to store the user's access token when they are not using CATcher.