Skip to content
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

Feature: better visibilty of palette catalogues #4057

Closed
knolleary opened this issue Feb 10, 2023 · 1 comment · Fixed by #4248
Closed

Feature: better visibilty of palette catalogues #4057

knolleary opened this issue Feb 10, 2023 · 1 comment · Fixed by #4248

Comments

@knolleary
Copy link
Member

The palette manager can be configured with multiple catalogues of nodes. It currently defaults to the catalog provided by flows.nodered.org.

If a custom catalog is provided, its contents are included in the search results within the palette manager - but there's no way of knowing which catalog a result comes from, or to be able to restrict search results to a particular catalogue.

This issue is to improve the UX of the palette manager when multiple catalogues are configured.

Ideas to look at:

  • Allow search results to be filtered by catalogue
  • Include catalogue information against individual search results
  • Look at how a catalogue with basic auth applied could be handled
@MarianRaphael
Copy link

Feedback from veloce-cloud on FlowFuse/flowfuse#217

"It will be nice to filter either node catalog by Open Source license type as well and date last updated."

@Steve-Mcl Steve-Mcl linked a pull request Jul 13, 2023 that will close this issue
6 tasks
@knolleary knolleary added the fixed label Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants