Enable autocomplete for undeployed seqera-config nodes #31
Conversation
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
Previously, autocomplete for launchpad names and data link names would only work after the seqera-config node had been deployed. This was because the backend could only retrieve config node properties via RED.nodes.getNode(), which only returns deployed nodes. This change enables autocomplete to work immediately after the config node is saved (closed with Done/Update), without requiring deployment: Frontend changes: - Use RED.nodes.node(configId) to get config from editor state - Pass baseUrl and workspaceId as query parameters to backend - Use params.set() for workspace override to ensure precedence Backend changes: - Accept baseUrl/workspaceId from query params when config not deployed - Use RED.nodes.getCredentials(configId) to look up saved API token - Add explicit credentials check before making API calls Files modified: - nodes/workflow-launch.html - nodes/datalink-list.html - nodes/datalink-poll.html - nodes/workflow-launch.js - nodes/_utils.js 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
🐳 Docker PR Build
|
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.
Summary
RED.nodes.node()in the frontend to get config values from editor stateRED.nodes.getCredentials()in the backend to look up saved API tokens for undeployed config nodesProblem
Previously, when configuring nodes like
workflow-launchordatalink-poll, the autocomplete functionality would only work after the seqera-config node had been deployed. This meant users had to:This was frustrating for new users setting up their first flow.
Solution
The autocomplete now works as soon as the seqera-config node is saved (clicking "Done" or "Update" in the config dialog). No deployment required.
Frontend changes:
RED.nodes.node(configId)to access config node properties from editor statebaseUrlandworkspaceIdas query parameters to the backendBackend changes:
baseUrl/workspaceIdfrom query params when config node isn't deployedRED.nodes.getCredentials(configId)to look up saved API tokenTest plan
🤖 Generated with Claude Code