RESEARCH:
- spread prop for react. Why? Why not?
IMMEDIATE:
(need to start using tandem to build itself completely)
- Paperclip
- VSCode extension wire up
- Tandem
- Components Pane
- DND components to existing components
- CSS Inspector
- toggle eye
- add declaration
- delete declaration
- edit declaration
- add style rule (auto add to scoped style element)
-
:root
inspecting
- Components Pane
HIGH PRIO:
-
paperclipc
- edit lib (need mutations module)
- Must work with firefox
-
Native elements pane
-
Components pane
- + button
- DND elements to stage (create new window)
- insert preview for elements that do not have one
- DND elements to other elements
- native elements
-
Paperclip
- [ ]
PROBLEMS:
- views not need props by react components
POSSIBLY:
-
Paperclip
- implement "is" with components
- can do neat diagrams about grouped elements
- ability to inherit styles (assuming it matches spec)
- implement "is" with components
-
show inferred types for component as they're being coded
FOCUS
- Safety is #1 priority
- type safety
- [ ]
- Warnings & Errors for paperclip
- Must be able to code everything visually (conditions as well)
V0 (before launch)
- paperclip
- v1.5 type inferences
- remove component properties -- scan for them.
V1
- Paperclip
- content editor (need mutations lib)
- warn when component id overriden
- Linter
- Stage tools
- highlight dynamic bindings
- [ ]
- CSS Editor
- add new style rule
- add new style declaration
- box shadow editor
- background color editor
- filter editor
- measurement converter (px <-> %)
- :root editor
- var() editor
- text editor integration
- vscode
- [ ]
- vscode
- Components pane
- promo
- ui kit
- Type safety
- Display error when component is missing a prop (even with spread operator)
- Display banner error for syntax errors
- Website
- Example on site
- Screenshots
- visual difference?
V2
-
Paperclip
- strong types
- source maps support
- i18n errors
-
Tandem
- Components filter
- Themable
V3
- Notes
- Git integration
- FSM - connecting UIs
- Screenshots