Up-to-date docs

[breyed]

The readme intro starts with this paragraph:

The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators. Using Rx, developers represent asynchronous data streams with Observables, query asynchronous data streams using LINQ operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, Rx = Observables + LINQ + Schedulers.

Two of the three links are to pages that have the notice, "We're no longer updating this content regularly." The doc path listed on each page is "Docs / Previous Versions / .NET / Reactive Extensions". Where should we confidently go to find up-to-date documentation on the current version of Reactive Extensions for .NET?

[danielcweber]

The best place currently would be http://www.introtorx.com/ I guess. AFAIK, there is no up-to-date class reference docs. The old Microsoft docs were given to the community lately, but they are in a rough shape.

[RLittlesII]

ReactiveUI has an open Pull Request reactiveui/website#192 to clean up some of this documentation and add it to https://reactiveui.net

[BenjaminHolland]

The *xAsync.Net packages are especially bad, because it's not at all clear how these packages are intended to be used or what problem they're solving, and they have no equivalents in the standard Rx educational resources. The same goes for the new operators like ForkJoin or Expand, which could really benefit from some additional explanation.

[bartdesmet]

It'd be great for the community to contribute to documentation.

As for the async variant of Rx, that effort is pretty much a work in progress (not to say it's merely a prototype at this point).

The async variant of Ix has been split into System.Linq.Async and System.Interactive.Async with the goal being for the former to move closer to the heart of .NET (whatever that is to be defined as) as the mirror image of System.Linq for IAsyncEnumerable<T>. The docs there should be trivial and straightforward, given it's a carbon copy of the original LINQ to Objects functionality ported to the async space.

[doxxx]

introtorx.com is dead. reactveui.net has no API docs for System.Reactive.* namespaces.

[quinmars]

Well it has. It is just a little bit hidden, because it is not in the API tab. As an example: https://www.reactiveui.net/reactive-extensions/buffer/

[doxxx]

That appears to be simply a (bad) copy of the docs on MSDN. For example, BehaviourSubject is not up to date.

[cabauman]

I have a task in progress to improve/update that "bad" (I agree) copy of the docs, which includes parsing the xml documentation from the dotnet/reactive repository: reactiveui/website#441.

[bartdesmet]

Some work is starting over at dotnet/docs#21325.

[RLittlesII]

@bartdesmet can we close this as it is being tracked in dotnet/docs#21150

[bartdesmet]

I'd suggest to keep it open here until the first cut has really been published, and we ensure that it's more up to date, as the title of this issue suggests. Starting from the legacy MSDN docs port is a good first step, but is a flashback to 2011 on which we then need to build (to at least address the major changes that went into Rx 2.x (which are larger than what happened in 3.x and 4.x combined).

Let's close this when the docs are published and we do some work in this repo to have some links up in the top-level README.md file so folks know where to go to read up on concepts and APIs.