Skip to content

Conversation

@krishna9358
Copy link
Contributor

Summary

Issue: The Console Log component only accepted a single data input, making it cumbersome to log outputs from multiple components. Users had to add multiple Console Log nodes to debug different parts of their workflow.

Solution: Updated Console Log to support multiple named input fields :

  • Added variables parameter with variable-list editor to define custom input fields
  • Implemented resolvePorts() to dynamically create input ports based on user-defined variables
  • Each variable can have a name (port ID) and optional label (display name)
  • Default data and label inputs remain available for backward compatibility
  • All connected inputs are logged with their labels for easy identification

Additional Fix: Fixed a bug in workflow-runner.ts where resolvePorts() wasn't being called for components with dynamic inputs, causing input parsing to fail.

Version: Bumped to 2.0.0

Testing

  • bun run test
  • bun run lint
  • bun run typecheck
  • Additional notes:

Documentation

  • Updated the relevant doc(s) (see docs/guide.md) or checked that no updates are needed.
  • Recorded contract/architecture changes in both public docs and .ai logs when applicable.

@chatgpt-codex-connector
Copy link

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@LuD1161 LuD1161 changed the title feat: added feature to support multiple dynamic inputs feat: Support multiple dynamic inputs in Console Log component Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants