Embedding caniuse data in event documentation

[Xavientois]

If we want to take this one step further we could look at somehow embedding the appropriate data from the caniuse repo? That is well beyond the scope of this PR, so I will make another issue for this.

Originally posted by @Xavientois in #1945 (comment)

This might be handy for folks using events, but wanting to be aware of where they might not be supported.
Not sure how useful others think this would be, but I'd be down to give it a try.

[hamza1311]

I don't think it's a good idea. It puts the maintainability burden on us. Anyone who wants to use a feature and is worried about it's support could just go to caniuse themselves

[Xavientois]

That's fair. I guess the core problem I would want to see about addressing is less an issue in Yew and more an issue with the web on the whole.

What I would maybe picture instead could be a warning that the user could toggle on or off in their project that would throw a warning on compilation when they are making use of a non-standard feature.

One of the reasons I like the idea of using Rust in frontend web dev is that it gives us the assurance of compile-time checks, thus instilling confidence that the code works before it breaks at runtime. That's sort of the goal behind this proposal. I'm open to other ways of achieving that; I'm not tied to this approach.

[teymour-aldridge]

I think the cost of adding a feature for this outweighs the benefits. We can definitely add a note emphasizing that these are non-standard attributes, but at some point the end user has to assume some responsibility for ensuring correctness. IMO the correctness budget is better spent on other things.

…

On 09/07/2021 16:14, Xavientois wrote: That's fair. I guess the core problem I would want to see about addressing is less an issue in Yew and more an issue with the web on the whole. What I would maybe picture instead could be a warning that the user could toggle on or off in their project that would throw a warning on compilation when they are making use of a non-standard feature. One of the reasons I like the idea of using Rust in frontend web dev is that it gives us the assurance of compile-time checks, thus instilling confidence that the code works before it breaks at runtime. That's sort of the goal behind this proposal. I'm open to other ways of achieving that; I'm not tied to this approach. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1948 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKFSTPIS6FCLA6CEMNJRW4LTW4G4JANCNFSM5ACWI7SQ>.