-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Custom API keys should be a table #10926
Comments
Hi, I would love to work on this issue. Can you assign it to me? |
As a general advice for newcomers: check out Contributing for a start. Also, guidelines for setting up a local workspace is worth having a look at. Feel free to ask here at GitHub, if you have any issue related questions. If you have questions about how to setup your workspace use JabRef's Gitter chat. Try to open a (draft) pull-request early on, so that people can see you are working on the issue and so that they can see the direction the pull request is heading towards. This way, you will likely receive valuable feedback. |
* Convert "Custom API keys" list to a table. * Handle if user clicked "check connection" without selecting a key. * update CHANGELOG.md * Handle if user clicked "check connection" without selecting a key in a better way. * Disable editing the "customApiKey" if "useCustomApiKey" is no cheked * Disable "Check Connection" button if no API key is selected. * add a new line to match to coding style * Bind the 'useCustomApiKey' checkbox with the emptiness of the 'customApiKey' field. * Update logic for "Custom API key" table to align with previous implementation * Add a note to guide users on how to commit changes
The UI of our preferences for Custom API keys is not that good:
I would like to have a table. We have n < 10 fetchers with API keys, thus this is not a long list.
I also renamed "Custom" to "Use Custom Key", to make clear that the given key should be used.
The text was updated successfully, but these errors were encountered: