-
Notifications
You must be signed in to change notification settings - Fork 25.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
Odata Documentation #11770
Comments
As long as the security implications and mitigations are covered I have no problems. |
@FIVIL can you post an outline here? |
@Rick-Anderson Sure.
for the first one i do not intend going into details so ill make a single article .
also i will add some code examples and i might include some screenshots from postman to showing the result of invoking the API for the second part i intend to make a couple of articles and in them i will go further into details and internals of OData
article number 4 -> adding model classes:
article number 6 -> Configurations of the project:
article number 7 -> Scaffolding
article number 8 -> Pushing some data into API
article number 10 -> Security concerns so im expecting to do this in at least 3 RRs one for article number 1, one for series of articles in 2nd part and one last PR for code examples |
@Rick-Anderson Sure, honestly im having some spare time within next few month and i want to get best out of it by contributing to aspnet repos, so im open to help with any task that can be done by community. |
@guardrex sounds great to me, so im waiting to hear from you. |
@FIVIL ping me next week if @blowdart doesn't approve your outline. @scottaddie / @danroth27 please review outline. |
Harsh but fair @Rick-Anderson. Security to 10 maybe? My concern here is, for example, someone reads enough to expose their data because that's what they want to do, without understanding they now have a DoS vector or Information Leak via joins. Notes in each section to the security section would work though, so no objections to the outline |
@blowdart sure, ill keep your notes in mind. |
so im trying to deliver first draft as soon as possible. |
@Rick-Anderson TNX |
@FIVIL looks great. Create a PR then I'll submit some commits to your branch for minor edits. |
@FIVIL when you submit the PR, |
@FIVIL I moved two of them over - see https://docs.microsoft.com/en-us/odata/webapi/odata-expand |
I want to add a few articles (and code examples as well) about Odata support in ASP.net core so as required in CONTRIBUTING.md file for complex submissions i opened this issue to get approval for them.
what i have in mind is a simple example of adding odata capabilities on top of existing API and also some tips for scenarios which include starting a new API project with odata support from scratch.
also i come across this (#9740) open issue about odata so i was wondering should i do it or wait for odata official team.
also i think it worth to mention that im having 1.5+ years experience with ASP.net core and 3+ years experience with C# and ASP.net mvc (.net framework) and also good understanding of odata.
@Rick-Anderson edit:
Reopen this and PR #12108 When MicrosoftDocs/OData-docs#74 is merged. Look for closed issues with ODATA
in:title
The text was updated successfully, but these errors were encountered: