Ironclad / Ironclad/rivet

[Feature]: HTML rendering node

Open
#314 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### Feature Request

...HTML rendering node, that way can easily add ui components, I'm thinking maps, nice display of results etc.
Could fire http calls at myself as some kind of output, that way can make a dashboard of buttons that fire graphs to run.

It looks like if a comment field can have a node as input, it already renders html!! 🙂

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

The issue does not name files, tests, or an entry point. Start by locating the node implementations and the comment-field rendering path, then clarify the supported HTML output, security boundaries, and dashboard interaction model; the work is done when that scope and its acceptance tests are defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.