Prev Wong

chore: export default layer components

4

Closes #412

fix: register connectors on useEffect()

1

Closes #404

Future of Craft.js - taking it to the next level! 🚀

10

# Background Hey folks! Craft.js is about 3 years old now and in that time we've seen plenty of Craft-based page editor implementations in the wild. I'm incredibly grateful for...

## Overview Currently, Reka resolve variables by their names and scope: ```jsx { type: "Program", globals: [ { type: "Val", name: "counter", ... } components: [ { type: "RekaComponent", name:...

feat: disallow data types in extension state

2

This PR adds an restriction that prevents storing any Reka data types as part of an `Extension` state

Code generation

1

Would be interesting to explore if we can take Reka's `State` and generate usable Javascript (ie: React) code. This would enable consumers to generate the output of the end-user designs...

Create an invalid `Type` throws an error that's difficult to read/debug: ```tsx import * as t from '@rekajs/types'; t.binaryExpression({ left: t.componentTemplate(...), // invalid, throws an error that's difficult to read...

In order to create easy-to-use high-level UIs surrounding defining new variables in Craft.js - we need a way to specify the type/kind of variables (ie: string/number/boolean/any)

The evaluator has caching points to prevent unnecessary re-evaluation. However, when any descendant of a `TagTemplate` gets re-evaluated; it will cause all of its ancestor `TagTemplate` to re-evaluate its props...

Consumers of Reka will likely store the `State` data structure in a database of some kind. However, we should anticipate that any existing `State` structure may become invalid in the...