Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdates to documentation #121
Comments
|
@kroniak Could you suggest how best to document supported platforms (as of Flurl 2.2)? Here is how the docs currently read:
I want to highlight .NET Core obviously. Do we say ".NET Core 1.0+"? What about targets such as NETStandard and UAP? They imply a collection of platforms, so they probably would not belong on this list, correct? Also MonoTouch/MonoAndroid are the same as Xamarin.iOS/Xamarin.Android, right? We're in your world here, so any advice is appreciated! |
|
@tmenier I think that the best is list target as in nuget package. About netcore say "Support NETCore 1.0.0 by NETStandard target 1.4". Like so. You write something and we will review. |
|
@kroniak How's this?
|
|
Hard to find good examples. NUnit lists theirs: https://www.nuget.org/packages/NUnit/ |
|
@tmenier Yep. I would have said: Minimal version:
|
|
@tmenier I'd suggest to document the work done for #222 on https://tmenier.github.io/Flurl/client-lifetime/ |
For tracking updates and changes needed to the docs. I welcome community input here!
https://flurl.io/installation/
https://flurl.io/fluent-url/
https://flurl.io/testable-http/
https://flurl.io/configuration/
https://flurl.io/docs/client-lifetime/#using-flurl-with-an-ioc-container
FlurlClientin service ctor - it's not thread safe. WhenConfigureClientis added toFlurlClientFactory, advise using that in service registration as I mentioned here.