codemile
commented
5 months ago I don't think this is a stable feature, as users would have side effects from the HTML and then ask the core team to fix them. It would be very difficult for us to track down if the HTML was the bug or something in Rivet. Further more, HTML isn't enough, as anything like a "map" would require JS dependencies, CSS including, etc. all of which would pollute the browser state and have buggy side effects.
Anyway, let's backtrack a bit here and discuss what "outcomes" you're trying to achieve with your solution. What is it you would be doing where you would need HTML? What does it help you do?
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