Jens Reimann

When dropping a file and then something else, the files still seem to be present in the state. I don't see any way to figure out what the last dropped...

Making the `use_async` a bit more ergonomic

3

I really like this project, especially the `use_async` hook. However, evaluating the state when rendering feels a bit verbose. It feels to me as if this could be improved a...

use_async with a parameter from state

2

Assuming a use-case of: * Enter a parameter value * Issue the request (with that parameter) It looks like with the current `use_async` variant, the future already gets created with...

Allow to send arbitrary extension attributes

1

Summarizing the chat discussion with @rmja … It would be good to allow devices (protocol endpoints) to send arbitrary header fields, which translate into CloudEvents (CE) extension attributes. As some...

Create a nicer overview page

1

Currently the overview page in the console lists all kind of information. Without giving any information what this means. We should create a nice (visually appealing and informational) page which...

While there was a decision to only act on changes, it might be ok in cases where the number of applications is low, to still do a periodic reconciliation.

This adds some internal infrastructure for adding more MQTT endpoint dialects. Also doing some example work with: * Web of Things * Cumulocity * Azure IoT

Currently we show the event stream in the "debug" tab on the console. Additionally, we peek at the application logs ourselves when stuff goes wrong (behaves unexpectedly). We should enable...

Long lived connections load the application and device information once, but then keep the originally loaded state until the connection is terminated. One exception is the MQTT endpoint, which already...

* Create using `drg` * Test all variations as with the username/password ones