ijk that returns an opinionated Virtual DOM schema out of the box?
See original GitHub issue@lukejacksonn If https://github.com/hyperapp/hyperapp/issues/578 lands, would you consider changing ijk so it can be used like this:
const { h } from "ijk"
h(['h1', 'Hello World'])
…without a call to h('name','props','children')
to create the actual h
function? In other words, have the exported h
return an opinionated Virtual DOM schema like { nodeName, attributes, children }.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Change internal VNode data structure. · Issue #578 - GitHub
I'd like to discuss the possibility to change our internal VNode data structure name and props fields to nodeName and attributes ...
Read more >Virtual DOM and Internals - React
The virtual DOM (VDOM) is a programming concept where an ideal, or “virtual”, representation of a UI is kept in memory and synced...
Read more >Zwn - River Thames Conditions - Environment Agency - GOV.UK
Unlp odontologia la plata, Kky-271i, Container wars season 1 online, ... Grooming definition in spanish, Eventbrite box office, Restaurant klenert ...
Read more >ReactJS | Virtual DOM - GeeksforGeeks
Virtual DOM: React uses Virtual DOM exists which is like a lightweight copy of the actual DOM(a virtual representation of the DOM). So...
Read more >LNCS 2814 - Conceptual Modeling for Novel Application Domains
at ER 2003, out of which we selected the following four based on peer reviews: ... Finally, the International Workshop on XML Schema...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It would be much nicer if we didn’t have to pass a schema so yeh, I would certainly consider it. Another option I thought of is to be able to pass
ijk
anh
to try figure out what schema it should output… something like:Either that or export different
h
for each vdom type:I am up for exploring all of these options!
@lukejacksonn I think using the framework’s exported VDOM builder function is far more robust than my proposal, but if you are willing to take the “risk”, returning the raw VNode object would make ijk even more fun to use. Whether you implement this feature or not is up to you. You did a great job here!