@edsolater/pivkit
v0.0.35
Published
1. _STATIC_ means that the prop is not reactive and will changing it will not trigger a rerender\ 2. all are optional
Downloads
406
Readme
props
Piv's(global props)
- STATIC means that the prop is not reactive and will changing it will not trigger a rerender\
- all are optional
if?: MayFn<BooleanLike>>
--- STATIC. if is settled and is false , it self and it's children will not renderifSelfShown?: MayFn<BooleanLike>>
--- STATIC. if is settled and is false , only it's children will renderdebugLog?: (keyof PivProps)[]
--- only use this for debug mode. it will log all you needdomRef?: MayArray<CallbackRef<any> | null | undefined>
--- accept domSetter(return from createDomRef) to access the domclass?: MayArray<ClassName<Controller>>
--- htmlElement's classid?: string
--- id foruseComponentByID
. So others can access component's controller without setprops:controllerRef
to component, this have to have access to certain component instance
special
- render -
render_SUBCOMPONENT
orrender_item
- TODO:
layout
ICSSBlock (style)
determin what component looks like
Component (UI)
<Piv>
base component. all other components is based on this<AddProps>
base component. StateManager is based on this
Box Component
<Box>
base component. all box-like components is based on this
Content Component
<Text>
ui text
PluginContext (UI)
<PluginContext>
base component. all other plugin components is based on this<EditablePluginContext>
with editablePlugin
StateManager (UI)
if use hooks to hold state, the user's component's code will be too complicated to understand
<Detector>
detect state (hover)
useKitProps - a very important hook
Main idea:
- normal props can accept promise and fn which return value
Q&A
what is different from props:variant
and props:icss
?
props:icss
reflect componet's verbose style, which is the "looks like" of the component.props:variant
reflect component's state, which is the "is like" of the component.