Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consumer Flow Creating Issues

Open
#19 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
html
Domain
frontend

Research direction

Start by reproducing the consumer flow with the Thing URLs in the issue, including actions without inputs and properties without types. Check the deployed-dashboard behavior with two UIs and determine whether it belongs to this plugin or FlowFuse. Done means all four reported behaviors have an identified owner and verified fixes or documented limitations.

Written by the indexing model from the issue text.

Description

  • TD is not accepted if the action does not have an input. Pasting http://plugfest.thingweb.io:8083/testthing gives tdAction.input is undefined. First, we should be more flexible since not all actions have an input. Second, the error should be pointing to the action if we want to show the error.
  • Same for properties. I get DATATYPES[tdProperty.type] is undefined when there is no type. This has no type: http://plugfest.thingweb.io:8083/counter for countAsImage
  • It would be better to add an invoke button to actions and a message saying "action invoked". Enter gives feedback if the action works as intended but if the action does not work, I cannot be sure if I managed to invoke it in the first place. Something similar would be good for properties and events as well, i.e. "property X read" etc.
  • Not sure if this is from the plugin or from flowfuse, but when I have two UIs deployed, pressing on "Open Dashboard" on the second thing's flow brings me to the first thing's UI.

Otherwise, it works

Dominant language
HTML
Stars
6
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-thingweb/node-red

All issues in eclipse-thingweb/node-red

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.