Emi
Interesting issue! This sort of opens thq eustions: 1. Do we remove `prop.Href` and require users to use `vecty.Attribute("href", "link")` ? I don't like this because it's less type safe...
Same issue with the `disabled` property on inputs I have found.
Thanks for filing this :) this is something I really want to look into soon.
No clue why I tagged this as long term, this seems important for 1.0.
Respectfully, I disagree. IMHO the React ecosystem is a mess because there are so many options and non-canonical ways to do things. This has led to the creation of projects...
Yes, issues like #148 come to mind actually. Currently, I view the [`arch-design`](https://github.com/gopherjs/vecty/issues?q=is%3Aissue+is%3Aopen+label%3Aarch-design) tag as issues that may affect the core in some way (but obviously, some issues like this...
Yes, that is something to look into. On Sep 2, 2017 6:39 PM, "Peter Fern" wrote: > Any thoughts on perhaps using WhatWG documentation instead? Producing a > locally maintained...
If we can find something that outlines the APIs signatures (symbol names and data types), then we can use a more additive approach (i.e. to ensure we have good coverage...
Since the Blink repository is over 5 GB and cloning it takes quite a while, I've created a subrepo that will host just the `*.idl` files from the blink repository...
@myitcv (spelled the name wrong)