I wonder if there's any way to avoid an extra wrapper tag? What I me

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Avoiding the extra wrapper tag? about superfine HOT 6 CLOSED

jorgebucaran commented on August 24, 2024

Avoiding the extra wrapper tag?

from superfine.

Comments (6)

jorgebucaran commented on August 24, 2024

@mindplay-dk Can you show the code with the current result body and the result you want?

from superfine.

mindplay-dk commented on August 24, 2024

Uhm, well, let's say I have a static page with some kind of layout.

<body>
    <div class="header">.....</div>
    <div id="fancy_app"></div>
    <div class="footer">.....</div>
</body>

And then something like:

import { patch, h } from "picodom";

function view() {
    return
    <div class="woot">
        <h1>Boom!</h1>
    </div>
}

patch(document.getElementById("fancy_app", {}, view());

Now I end up with:

<body>
    <div class="header">.....</div>
    <div id="fancy_app">
        <div class="woot">
            <h1>Boom!</h1>
        </div>
    </div>
    <div class="footer">.....</div>
</body>

So now, the top-level node of the actual view is div.woot, but it's wrapped in div#fancy_app - one of those two would have likely been enough, but... I guess JSX syntax forces you to always return a single parent node, and you have to have another reserved node to render into, whether that's body or something else...

I don't know, maybe it's no big deal? I only brought it up because hyperHTML, using template strings, allowed me to render multiple nodes into a target container - but I guess maybe the limitation here is actually JSX syntax itself?

from superfine.

jorgebucaran commented on August 24, 2024

@mindplay-dk Okay, I understand now. Picodom doesn't have the ability to return an array of elements in the top level container, but component can return arrays of elements.

However, there is currently no way to tell Picodom to replace the given container and if there was, what would happen when you pass document.body?

from superfine.

mindplay-dk commented on August 24, 2024

Good point about the document body, yeah, that wouldn't even make any sense.

In my mind, I'm trying to turn this into a good thing - the fact that every view or component has precisely one root node actually makes the whole app (and framework) much simpler and easier to reason about. Maybe "fixing" this isn't even a good idea?

from superfine.

jorgebucaran commented on August 24, 2024

@mindplay-dk This is one of the reasons the container was optional. So, that default behavior would be append to document.body without wrapper elements.

from superfine.

mindplay-dk commented on August 24, 2024

I think there's nothing actionable here, so I'm closing this issue.

from superfine.

Recommend Projects

Avoiding the extra wrapper tag? about superfine HOT 6 CLOSED

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent