Alex Moldovan

## Context Event handlers are still an experimental feature in the UIDL, but currently it supports `stateChange` and `propCall` as two different statements. ``` "click": [ { "type": "stateChange", "modifies":...

## Context When using a dynamic node, we reference the exact value of that prop/state/local var. Like in this example: ``` { "type": "dynamic", "content": { "referenceType": "prop", "id": "title"...

This is not necessarily a common case, but it appears in a lot of examples, where you would define a component in React for example: ```javascript class MyComponent extends React.Component...

Async generators can be made sync?

2

Initially we developed the component generators as async functions, but since the flow is sync, it might not be needed after all. A resolution would be great before the official...

It might be useful at some point to render something based on two different state keys. Currently this could be done in theory, but in a hackish way with nested...

Implement smart conditional renders

2

We had this implemented (#89 and #103) but with the new UIDL structure, this has to be thought differently. Perhaps we can have a step in the resolver that looks...

Describe layout component from UIDL

1

Currently we assume that the first node inside the `root.content` is describing the different `routes/states` of the application. We may want to describe some sort of layout component around the...

feat(create-ws): new step for use cases

1

A new step is added in the create-workspace flow  For testing, you can use any existing FREE workspace by going to /create-workspace?workspace= and click next on the first step....

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of...