Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore #3

Open
39 of 80 tasks
lifeart opened this issue Dec 29, 2023 · 2 comments
Open
39 of 80 tasks

Explore #3

lifeart opened this issue Dec 29, 2023 · 2 comments

Comments

@lifeart
Copy link
Owner

lifeart commented Dec 29, 2023

@lifeart
Copy link
Owner Author

lifeart commented Jan 12, 2024

Error recovery notes, there is 2 possible options for error:

  1. Rendering stage. Here we could wrap with try/catch [feature] render-error-overlays #55
  2. Updating stage, at the moment we removing broken opcode from stack, but better approach will be: register opcode with closes parent (component instance), and re-mount it as we do for-hot-reload.

@lifeart
Copy link
Owner Author

lifeart commented Jan 15, 2024

Compilation pipeline notes:

TextContent:

  • every primitive should be wrapped to SYMBOLS.TEXT to avoid runtime iteration (or not?)
  • every path should be wrapped to RESOLVE_RENDERABLE (should it be smart to remember resolutions per classes?)

Attributes / Properties:

  • no pre-mapping here for primitives, but wrapping to RESOLVE_RENDERABLE paths

Slots:

  • should be wrapped to UnstableChildWrapper and it should belongs to slotOwner? slotUser?

--

If we starting to resolve values on render/append level, we need to transfer destructor to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant