Is there a way to remove a child from a parent element?

[alessioarena]

In the past to remove an Element or MacroElement from its parent I used del parent._children[childName], but that seems a buggy operation. In several cases when rendering the parent the child is still there.

Is there a preferred way to remove a child from a parent element?

An example of the issue I'm having: Adding a Draw element to a Leaflet map using Folium

Parent has the draw_control child

JavaScript code injected to the resulting HTML element

Now I removed the child from the _children attribute using the method above:

The Draw element is still there when rendering!

and the JavaScript code is still there

[RohanG0407]

@alessioarena Any solution to this issue yet? I'm trying to delete a Marker frop the map by deleting its child in._children. It seems that the child get deleted from ._children but the Marker is still on the Map.

[alessioarena]

Unfortunately not at the moment. I think is something to do with the rendering of the leaflet map already done once with the child, and probably cached somewhere. However I could not find a solution apart from copying the children and attribute of the map to another brand new Map object. I can send you the snippet of code that worked for me if that is helpful

[alessioarena]

This is what I'm currently doing to copy a Map object:

def copy_map(map_obj):
    new_map = folium.Map()
    new_map.options = map_obj.options
    for k, v in map_obj._children.items():
        new_map.add_child(v)
    return new_map

You can then remove the child before is rendered, or just not add it in the first place by modifying this function and capturing a condition (child name, index and so on).

I'm not sure if that is generalized enough, there may be other attributes that you would like to copy to the new object, but for my case it worked

[Conengmo]

When we render, objects are added to the header, html and script attributes of the Figure object. To delete something, it has to be deleted there as well.

The way things are set up pretty much assumes a user renders once and that's it.

Thanks for sharing your workaround @alessioarena. I'll close the issue for now. If somebody wants to think about a cleaner, native way of deleting items, that's welcome.