-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Wiki link to project.json schema doesn't reference current schema #440
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
Comments
http://json.schemastore.org/project-1.0.0-beta4 has the latest changes |
Ah! ... then it's just the link to the schema at: https://github.com/aspnet/Home/wiki/Project.json-file ... that should be updated. However, on-going betas may be limiting your ability to keep that link in the Wiki up-to-date until release. I'm going to close this now. |
Will do. We kept them separate for now just so we don't break older consumers. |
Gosh ... lots of significant deltas between the two files. I know keeping that Wiki link to the schema up-to-date might be a problem for next few months, but I wonder if it isn't a larger problem having newbies (like me) looking at such an old schema when we're jumping in for the first time. I can see that messing folks up. The Wiki link is under the "Schema" heading at: https://github.com/aspnet/Home/wiki/Project.json-file Actually, I'll leave this open and let you decide if you want to update the link or not and close this at your discretion. Thx, Luke |
That all depends, if you're using beta3 then it makes sense. The dnx changes aren't even done yet so the question is, what should the wiki represent? Bleeding edge or released? Or should it just point to both schemas. |
Good point ... and there is no way to provide a directory of all stored schema files with schemastore.org? ... then people could look and know (or guess) by filename which one they should be looking at (and it would also save your team having to keep that one link updated) |
Is it easier to read the schema or the wiki? |
Yeah, easier to read the wiki for sure. However, that schema link being the first thing on that page ... and my being newbie ... I clicked to open that schema file and started reading it carefully. That's really not a good idea given the deltas to the latest version for a newbie about to jump in at CTP7. I guess what you're implying is that the Wiki (or parts of it) might be 'last CTP beta' ... beta3 right now ... and not 'bleeding edge (dev branch) beta' or 'trying to learn for the next CTPx beta' ... beta4 right now. Maybe the way to go is just to add a note below that link that points to the schemastore JSON page:
|
Remove duplicated UseHttpsRedirection (#437)
Expose TraceIdentifier on Httpcontext
http://json.schemastore.org/project
Line #79: "description": "List of files to exclude from publish output (kpm bundle).",
The text was updated successfully, but these errors were encountered: