Support D3?
- Langage dominant
- JavaScript
- Étoiles
- 690
- Forks
- 25
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Part of the reason I created #1 was I wondered about using this to render `d3`.
I was reading the https://github.com/Olical/react-faux-dom/ source when I saw your Tweet about this project.
I'm not sure exactly what changes are required. I believe some will be small (like `ownerDocument`) or `namespaceURI` while others (like `style` and `querySelector`) will require more time and bytes.
FWIW, here's [their DOM support](https://github.com/Olical/react-faux-dom/blob/master/DOCUMENTATION.md#dom-support) and [their d3 tests](https://github.com/Olical/react-faux-dom/blob/master/test/d3.js). A key first step would be to get `d3.select(document.createElement('div')).append('p').node()` to return to newly created `
`.It seems like we can either a) add support for this use case into this document b) create another project which imports `undom`. Do you have a preference? Does this use case ([with limitations](https://github.com/Olical/react-faux-dom/pull/30)) seem like a fit for undom "core" or should it be an separate lib?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by reading react-faux-dom's DOM support documentation and test/d3.js, then try d3.select(document.createElement('div')).append('p').node(). The scope and whether this belongs in undom core or a separate project still need a decision; done is not defined beyond the requested D3 compatibility.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- d3, javascript
- Domaine
- frontend
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100