Conversation
…UI building - switched all double‑quoted strings to single quotes for consistency - aligned import statements and removed unnecessary spacing - condensed UI construction code with clearer layout definitions - refactored project and issue loading logic for better readability - added inline comments and minor variable renames without altering functionality - updated button definitions and loading indicator handling to match new style conventions
|
Include avatarLoader.js in extra sources for the extension build |
- Notify users and display a loading message when GitLab API returns 401 or 403, guiding them to set the server URL and token. - Clear and refresh project and issue lists in the selector and report dialogs to reflect the missing configuration. - Extend time‑sending component to show an error notification on authentication failures.
|
Thanks for the contribution! The improved error handling for 401/403 auth errors is a good addition, and catching the missing However, there are a few issues that conflict with the GNOME extension review guidelines I just addressed: 1. Use
|
…ity-issues Use console.debug(), trim verbose/sensitive logs, and simplify project loading
|
Thanks for working on this! I reviewed the final diff and found some issues that need to be fixed before we can merge: extension.js - Broken merge
issueSelector.js
reportDialog.js
Please:
|
The issue selector was not properly filtering or displaying available issues.
This commit fixes the selector behavior to correctly show and filter GitLab issues based on user input.