-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
#1731 Docs for 20.0 release #1754
Conversation
Review doc. Update by links. Add labels.
…lders & Future sections
@ggnaegi Do you approve? |
All features have been defined as sections with More here: reST Sections |
Ok, reviewing the docs :-) I would be up for the GraphQL bit, but with https://github.com/ChilliCream/graphql-platform, not graphql.net. I have some experience with HotChocolate, since I implemented GraphQL for a customer. this .net server is imho better and Michael (the owner) is a member of the GraphQL Technical Steering Committee. But that's my opinion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job! I have written two comments, but we should send a positive message to the contributors.
docs/features/qualityofservice.rst
Outdated
|
||
You must set a number greater than 0 against ExceptionsAllowedBeforeBreaking for this rule to be implemented. Duration of break means the circuit breaker will stay open for 1 second after it is tripped. | ||
TimeoutValue means if a request takes more than 5 seconds it will automatically be timed out. | ||
You must set a number greater than ``0`` against **ExceptionsAllowedBeforeBreaking** for this rule to be implemented. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here I would mention that the functionality is not working at the minute (see ticket).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have a bug in backlog, it doesn't mean we have to remove docs, right?
Make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or, would you like to mention this bug in docs?
Won't it be strange?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, great idea!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All NuGet package builds & releases are done with CircleCI `here <https://circleci.com/gh/ThreeMammals>_` and all releases are done from `here <https://ci.appveyor.com/project/TomPallister/ocelot-ayj4w>_`. | ||
All NuGet package builds and releases are done with CircleCI, see `Pipelines - ThreeMammals/Ocelot <https://circleci.com/gh/ThreeMammals/Ocelot/>`_. | ||
|
||
Only Tom Pallister (owner) and Ocelot Core Team members (maintainers) can merge releases into **main** at the moment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very negative way of explaining things. I wouldn't tell the contributors about the organizational details, and instead of writing "Do not mention Tom", I would use "Please, mention Raman".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! We need to be more pleasant maintainers. 🤣
I would prefer to replace Do not mention Tom
line by another phrase: "We do follow this dev and release process... bla-bla-bla"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Tom wrote a lot in docs, I would say If you need to do something which we won't do, please help yourself!
🤣
And, relevant version:
If you reference Tom in issues to help, who is not going to reply to you, please help yourself!
🤣
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not a fun to integrate custom libraries, except direct references to official libs. |
Mmh. Graphql.NET is not the official implementation by the way. There is no official implementation. |
Thanks!
I've fixed issues! Please, approve, if no other issues. |
@RaynaldM Hey, Ray! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok for me, thanks!
@RaynaldM Good morning, France! 😊 |
* Update README.md Review doc. Update by links. Add labels. * Update readme.md: Review doc. Update links * Update building.rst: Review doc * Update overview.rst * Update tests.rst: Review doc. Update links * Update releaseprocess.rst: Update development process * Update bigpicture.rst: Copy Welcoming from README * Update contributing.rst: Add discussions and dev process refs * Update gettingstarted.rst * Update gotchas.rst: Write IIS gotchas * Update notsupported.rst: Add sections. Use more links * Update administration.rst: Review doc. Fix markup. More links * Update authentication.rst: Review doc. Add more links * Update authorization.rst: review. Add "Authorization Middleware" section * Update caching.rst: Review markup. More links * Update claimstransformation.rst: Review doc. Update markdown. Middleware links * Correct spelling error in dev docs * Update configuration.rst: Review the doc. Rewrite "SSL Errors" section * Update delegatinghandlers.rst: Review. More links. Add "Order of Execution" section * Update dependencyinjection.rst: Review the doc. Fix markdown * Update errorcodes.rst: Review. Add "Design" section * Update graphql.rst: Review. Add "Future" section * Update headerstransformation.rst: Review. More links. Rewrite Placeholders & Future sections * Update headerstransformation.rst: Add "Global Headers Transformation" subsection * Update kubernetes.rst: Review. Links. Add K8s logo * Update kubernetes.rst: Add link to the parent feature * Update loadbalancer.rst: Fix markdown. More links * Update logging.rst: More links. Rewrite "Warning" section * Update methodtransformation.rst * Update middlewareinjection.rst: Review. Check links. Add "Future" section * Update qualityofservice.rst: Review markdown * Update ratelimiting.rst: Review. Markdown. Add "Future" section * Update requestaggregation.rst: Review. Fix markdown * Update requestid.rst: Review markdown * Update routing.rst: Review markdown. Simplify code blocks * Update servicediscovery.rst: Review markdown * Update servicefabric.rst: Review markdown * Update tracing.rst: Review markdown. More links * Update websockets.rst: Complete rewrite * Update README.md: Hide Coverage badge. More footnotes * Update README.md: Add "Service Discovery" footnote * Update index.rst: Arrange features. More instructions * Update releaseprocess.rst: Be more pleasant * Update qualityofservice.rst: Add QoS label and footnote * Fix Sphinx build errors & warning. Fix typos * Add bash script * Order feature names ascending * Sync & update scripts
Fixes #1731
This is the major update of the documentation for the current 20.0 release.
Proposed Changes
I guess, most interesting things to look at are:
git grep 'Future' release/20.0-docs