Skip to content

✨ feat(chaining): allow chaining with arbitrary json#87

Merged
jfbus merged 1 commit intomainfrom
input_no_json
Mar 4, 2026
Merged

✨ feat(chaining): allow chaining with arbitrary json#87
jfbus merged 1 commit intomainfrom
input_no_json

Conversation

@jfbus
Copy link
Copy Markdown
Contributor

@jfbus jfbus commented Mar 3, 2026

Description

This PR ensures that any kind of JSON data can be used for chaining.

It will try to unmarshal in the input struct, and silently fails if not.

The PR also replaces the Go templating engine with a jq based engine, allowing lists of values.

Type of Change

Please check the relevant option(s):

  • 🐛 Bug fix
  • ✨ New feature
  • 🧹 Code cleanup or refactor
  • 📝 Documentation update
  • 🔧 Build or CI-related change
  • 🔒 Security fix
  • Other (specify): ux

How Has This Been Tested?

Please describe the test strategy:

  • Manual testing
  • Unit tests
  • Integration tests
  • Not tested yet

Checklist

  • I have followed the Contributing Guidelines
  • I have added tests or explained why they are not needed
  • I have updated relevant documentation (README, examples, etc.)
  • My changes follow the Conventional Commits specification
  • My commits include appropriate Gitmoji

Additional Context

Base automatically changed from oos to main March 3, 2026 16:11
@jfbus jfbus changed the base branch from main to fix_params_case March 3, 2026 16:38
Base automatically changed from fix_params_case to main March 4, 2026 13:39
@jfbus jfbus marked this pull request as ready for review March 4, 2026 13:43
@outscale-rce outscale-rce added kind/bug Bug fix kind/feature New feature or request labels Mar 4, 2026
@jfbus jfbus merged commit a9c88b7 into main Mar 4, 2026
4 checks passed
@jfbus jfbus deleted the input_no_json branch March 4, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bug Bug fix kind/feature New feature or request

Development

Successfully merging this pull request may close these issues.

2 participants