Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Building out
raj-spa
I ran into the problem ofraj/runtime
not accepting aninit
function. Or to put it another way, I ran into the problem ofraj/react
using aninit
function. Both make sense in their own ways but for the community at large the difference is a huge pain. My goal has always been to have the runtime and React runtime apps be aligned so that they can benefit, within reason, from the same ecosystem.The solution was to lift the
init(props)
up one more layer. Which I think is the best move because in every app I have made with Raj I have only needed React (and thus props) at the root, once per app. So adding one more closure at the root is the best solution ergonomically. I also look forward to writingconst init = [model, effect]
as the function wrapper I always felt was verbose.