Replies: 3 comments 4 replies
-
|
Pinging @mdn/content-webassembly and @mdn/yari-content-javascript |
Beta Was this translation helpful? Give feedback.
-
|
cc/ @Rumyra |
Beta Was this translation helpful? Give feedback.
-
|
I'm not a member or collaborator, but I agree with the idea here.
This in particular makes it really weird to see |
Beta Was this translation helpful? Give feedback.
-
|
I intend to move all these pages under @Rumyra @MendyBerger @mdn/yari-content-javascript |
Beta Was this translation helpful? Give feedback.
-
|
OK, seems I've (silently) got the blessing I need. Went ahead to create mdn/content#20603 |
Beta Was this translation helpful? Give feedback.
-
|
@Josh-Cena Sorry, did not see this. IMO WASM is the right place. These are "really" Web APIs, but unlike the others they are intended primarily for toolchain developers not ordinary developers. I think that having them in WASM groups them where they are likely to be discovered by the users who need them. JavaScript section is definitely not the right place. That's for pure language features. |
Beta Was this translation helpful? Give feedback.
-
|
I also thought about web APIs, but ended up putting it in WASM for the reason you said (discoverability). I'm fine with either. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I find it very weird that
WebAssemblyis in the JS docs, because:WebAssemblyalready appears in the sidebar of https://developer.mozilla.org/en-US/docs/WebAssembly), and it's awkward when all issues/PRs that really target the WASM interface end up having the "Content:JS" labelCan we move this object to the WASM docs completely? This means removing "/JavaScript/" from the URL and removing it from the JS sidebar.
Beta Was this translation helpful? Give feedback.
All reactions