Add the ability to update user settings in the UI and in the backend, including entering and viewing the user's Canvas API token. The token is visible on the frontend right now when viewing settings. While this practice would normally be replaced with showing partial or no token at all for security purposes, given our use case I thought it easier to just show it. The backend contains an easy way to filter out sensitive fields if we decide to prefer that approach instead. I included settings.json to the .gitignore so that no secrets are leaked into the repo. This should allow you to safely delete any .env files and just enter your token in the UI or settings.json file manually.
Add the ability to update user settings in the UI and in the backend, including entering and viewing the user's Canvas API token. The token is visible on the frontend right now when viewing settings. While this practice would normally be replaced with showing partial or no token at all for security purposes, given our use case I thought it easier to just show it. The backend contains an easy way to filter out sensitive fields if we decide to prefer that approach instead. I included settings.json to the .gitignore so that no secrets are leaked into the repo. This should allow you to safely delete any .env files and just enter your token in the UI or settings.json file manually.