Skip to content

Custom API keys should be a table #10926

@koppor

Description

@koppor

The UI of our preferences for Custom API keys is not that good:

image

I would like to have a table. We have n < 10 fetchers with API keys, thus this is not a long list.

Catalog Key Use Custom Key
Biodiversity heritage test [x]
IEEE other [x]
Science direct my [x]

I also renamed "Custom" to "Use Custom Key", to make clear that the given key should be used.

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

Status
Done
Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions