Repository navigation
Conversation
fixes FlowFuse/engineering#534 Allow catalogue URLS to be added to team types and only added to devices and instance is they are not already present
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8946 +/- ##
=======================================
Coverage 80.01% 80.02%
=======================================
Files 476 476
Lines 26191 26199 +8
Branches 6982 6986 +4
=======================================
+ Hits 20958 20966 +8
Misses 5233 5233
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
Author
|
The failing UI tests appear to pass locally |
knolleary
requested changes
Nov 4, 2026
Member
There was a problem hiding this comment.
Whilst this works, had some feedback for bits that might need tidying up.
In both deviceLive.js and project.js
- Accesses
team.TeamType?.properties?.extraCataloguesdirectory. Should beteam.getProperty("extraCatalogues", null)so that it could be overridden at the team level - The check for that property assumes
response.palette.cataloguesexists. Earlier in the function is a check that initialises that property based on other properties. Not sure if there's a combination there that will trip us up - We only apply this setting if cert nodes is enabled - but at the TeamType dialog this is presented as a general option for additional catalogues that don't need to be certified. Either we want to make this option truly about adding catalogues without it being specific to cert nodes (move the work to append the catalogues out of the containing if block), or we update the dialog to be explicit this is about cert nodes.
URL.parse(cat)was flagged as a new API that cuts off Safari 17 which isn't that old. We don't use it in the code base already, so potentially breaking.
Contributor
Author
|
I've fixed 1, 3 and 4 As for 2, I think we are safe as cert nodes or ffnodes has to be enabled, so we will have injected at least one catalogue. |
knolleary
requested changes
Nov 9, 2026
knolleary
left a comment
Member
There was a problem hiding this comment.
Need to try/catch url constructor to handle invalid entries.
Co-authored-by: Nick O'Leary <nick.oleary@gmail.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes FlowFuse/engineering#534
Description
Allow catalogue URLS to be added to team types and only added to devices and instance is they are not already present
Related Issue(s)
FlowFuse/engineering#534
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel