wycats
Repos
274
Followers
10070
Following
11

Minimal templating on steroids.

16985
1962

Ember.js - A JavaScript framework for creating ambitious web applications

22387
4140

Fun and simple reactivity

242
12

Events

Bump deps

Make sure all preacts are the same

Retools useSetup

This commit introduces a way to use useSetup with the setup/compute pattern.

I intend for this to be the default way to introduce React users to Starbeam in the future. This will be coupled with documentation about the importance of the setup/compute pattern to Starbeam and a way to package up universal reactive objects that use the pattern.

Fix the demos (which were still using Component)

Introduce Custom/CustomBlueprint

The idea is to introduce a packaged up concept that useSetup can use directly. This clarifies the setup/compute model for basic reactive objects, and makes it possible to package up custom reactive objects that renderers can use directly.

TL;DR this is the start of clarifying and implementing a pattern for writing universal reactive code in a similar manner as we currently support writing universal resources.

My hope is that resources become a souped up version of Custom, and that the explanation for universality flows neatly from Custom to Resource to Service/Modifier.

🤞

Tweak API

Created at 12 hours ago
delete branch
wycats delete branch feature/react-use-setup-2.0
Created at 12 hours ago
pull request closed
React useSetup 2.0

This commit introduces a way to use useSetup with the setup/compute pattern.

I intend for this to be the default way to introduce React users to Starbeam in the future. This will be coupled with documentation about the importance of the setup/compute pattern to Starbeam and a way to package up universal reactive objects that use the pattern.

Created at 12 hours ago

Bump deps

Make sure all preacts are the same

Retools useSetup

This commit introduces a way to use useSetup with the setup/compute pattern.

I intend for this to be the default way to introduce React users to Starbeam in the future. This will be coupled with documentation about the importance of the setup/compute pattern to Starbeam and a way to package up universal reactive objects that use the pattern.

Fix the demos (which were still using Component)

Introduce Custom/CustomBlueprint

The idea is to introduce a packaged up concept that useSetup can use directly. This clarifies the setup/compute model for basic reactive objects, and makes it possible to package up custom reactive objects that renderers can use directly.

TL;DR this is the start of clarifying and implementing a pattern for writing universal reactive code in a similar manner as we currently support writing universal resources.

My hope is that resources become a souped up version of Custom, and that the explanation for universality flows neatly from Custom to Resource to Service/Modifier.

🤞

Tweak API

Created at 13 hours ago
wycats create branch main
Created at 1 day ago
create repository
wycats create repository
Created at 1 day ago
issue comment
[i18n] Intl getCanonicalLocales / RelativeTimeFormat / ListFormat > 2339 error

What's the deal with this?

Created at 2 days ago
issue comment
TypeScript 5.0 features

Although TS 5.0 also supports ES decorators, we will not add decorators transform to the preset-typescript like we did for other stage 3 features. Use the following config if you want to try ES decorators and TS 5.0 features:

{
  "presets": ["@babel/preset-typescript"],
  "plugins": [["@babel/plugin-proposal-decorators", { "version": "2022-03" }]]
}

What's the rationale?

Created at 2 days ago
issue comment
Nightly Typescript features not applied correctly

Now that this feature is in TypeScript 4.9, it's even more glaring that this still doesn't work.

Created at 2 days ago

WIP

Created at 2 weeks ago
pull request opened
[WIP] Draft of docs about instances
Created at 3 weeks ago
create branch
wycats create branch instance-docs
Created at 3 weeks ago

Introduce Custom/CustomBlueprint

The idea is to introduce a packaged up concept that useSetup can use directly. This clarifies the setup/compute model for basic reactive objects, and makes it possible to package up custom reactive objects that renderers can use directly.

TL;DR this is the start of clarifying and implementing a pattern for writing universal reactive code in a similar manner as we currently support writing universal resources.

My hope is that resources become a souped up version of Custom, and that the explanation for universality flows neatly from Custom to Resource to Service/Modifier.

🤞

Created at 4 weeks ago
issue comment
Support for auto-accessor fields from the Stage 3 Decorators proposal

Is there a reason not to implement a similar keyword for public readonly properties which would do the same, but without a setter?

More generally, is there a reason that readonly accessor isn't supported?

Created at 4 weeks ago
pull request closed
More-conservative-cjs-builds
Created at 4 weeks ago

Fix the demos (which were still using Component)

Created at 4 weeks ago

Bump deps

Make sure all preacts are the same

Fix lints (and don't run lints on the root)

This lint was a false positive

Disabling it caused type errors elsewhere.

We may want to disable prefer-return-this-type, but that's a topic for another PR.

Merge branch 'main' into feature/react-use-setup-2.0

Created at 4 weeks ago
pull request closed
Bump deps
Created at 4 weeks ago
delete branch
wycats delete branch deps/2023-1-3
Created at 4 weeks ago

Bump deps

Make sure all preacts are the same

Fix lints (and don't run lints on the root)

This lint was a false positive

Disabling it caused type errors elsewhere.

We may want to disable prefer-return-this-type, but that's a topic for another PR.

Created at 4 weeks ago

This lint was a false positive

Disabling it caused type errors elsewhere.

We may want to disable prefer-return-this-type, but that's a topic for another PR.

Created at 4 weeks ago

Fix lints (and don't run lints on the root)

Created at 4 weeks ago
pull request opened
React useSetup 2.0

This commit introduces a way to use useSetup with the setup/compute pattern.

I intend for this to be the default way to introduce React users to Starbeam in the future. This will be coupled with documentation about the importance of the setup/compute pattern to Starbeam and a way to package up universal reactive objects that use the pattern.

Created at 4 weeks ago
create branch
wycats create branch feature/react-use-setup-2.0
Created at 4 weeks ago

Make sure all preacts are the same

Created at 4 weeks ago
pull request opened
Bump deps
Created at 4 weeks ago
create branch
wycats create branch deps/2023-1-3
Created at 4 weeks ago
create branch
wycats create branch add-notes
Created at 4 weeks ago
pull request opened
More tutorial sections
Created at 1 month ago
create branch
wycats create branch feature/react-tutorial-resources
Created at 1 month ago