-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure all code examples are runnable #7293
Comments
Shouldn't we use the LTS because that's what's recommended on the home page? |
Maybe we should add a tag on each snippet called version="current" or version="lts" so we know which version to run the snippet against. And then we can also visually add the label with a tooltip so people know if the latest lts or current version support said feature |
The home page recommends 22 right now, which is ACTIVE. |
Wdym with active? 22 is LTS. |
If we go back to the idea of having the version for which the document was designed in metadata. This makes it possible to keep the code functional on a given version. |
At Collab Summit we discussed that there have been instances of the code examples not being runnable snippets.
There are many ways we could approach this, but they all have the same characteristics:
Whether or not the authoritative source code remains on the website or elsewhere represents work and pros/cons for website maintenance and approachability.
@bnb had some more thoughts on how to accomplish this, but I don't think we have any concrete approaches yet.
The text was updated successfully, but these errors were encountered: