-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Consider adding playground-specific metadata #1932
Comments
I would be happy to add whatever metadata. Are you able to submit a PR w/ that? |
How does one get Tokio 0.2 in the playground? |
The criteria is one of:
Generally, the only directly-actionable route is the cookbook.
I could. I assume that |
Yep, |
I guess once |
Yeah, we should def include it as |
Version
0.2.x
Description
With the changes in 0.2.x to use a feature-flagged
tokio
crate where everything is off by default, there's the possibility of Tokio not being shown in its best light on the playground.The playground has custom metadata that allows crate owners to opt in to what features will be enabled on the playground.
This is not an immediate concern as Tokio is currently only brought into the playground as a dependency (of hyper and reqwest), so whatever flags they use should be sufficient, once they update to 0.2.x.
The text was updated successfully, but these errors were encountered: