You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initial Braindump for re-architecture for ink-components 1.0
Minimal (if any) syntax changes for HTML elements
Move to typescript
Move to a more pluggable redux system that includes allowing it to be used in a larger application
This also means that cross-variable scope access should be relatively easy
Remove the IFrame creation by default and move to centralized redux
This means that by default execution of variables should happen in the same window, which is fine in most developed applications where the source is trusted
This is not ok with user-generated content, however, the pluggable redux system should be able to handle the abstraction in those cases
Provide the execution library for the functions, this could be replaced in the future.
Remove as many opinionated styles as possible and move to JSS and/or the lit element style updates
Regardless these should be pluggable
Remove boilerplate from the property creation if possible. Maybe through wrappers or post-processing the class?
Right now there is a ton of redundancy that is just setting up class properties, this could be done after the class is created? Object.defineProperties or similar?
Another goal of this is to express the properties as data so they can be used in other places
This will likely mean breaking up into a few different libraries that could be used independently (CV, Chart, etc.) which is hopefully more maintainable. Have a single repo of these packages.
The text was updated successfully, but these errors were encountered:
Initial Braindump for re-architecture for ink-components 1.0
window
, which is fine in most developed applications where the source is trustedObject.defineProperties
or similar?The text was updated successfully, but these errors were encountered: