Reactive: Easily half the methods on reactivex.io are listed as TBD under Rx.NET

[jcotton42]

As the title says, they really need to be filled in

[CindyKee]

It feels like this project has been abandoned - was it rolled into mainstream .NET, or is it just that everybody is focused on RxJS instead?

[bartdesmet]

We don't own reactivex.io. These methods exists and are documented in the XML documentation files that ship with Rx.NET.

[mattpodwysocki]

@bartdesmet @desertrambler I am a part of the reactivex.io team. The problem has been the lack of MSDN or markdown documentation to point to which is why things are TBD. We hope to work on that soon

[bartdesmet]

https://msdn.microsoft.com/en-us/library/system.reactive.linq.observable(v=vs.103).aspx would be a start.

[mattpodwysocki]

@bartdesmet it would be if it were on 2.x instead of 1.x as quite a few things are missing like TakeLastBuffer etc. We can talk about this offline

[akarnokd]

The reactivex.io site is driven by https://github.com/ReactiveX/reactivex.github.io which is not that easy to contribute to and has been outdated for many years. I'm not 100% certain but the maintainer(s) are subcontractors of Netflix who left the project in limbo some time ago.

[jcotton42]

Where should we go then for documentation?

[akarnokd]

https://github.com/dotnet/reactive/issues/180#issuecomment-220158992 . The rest is search engines and StackOverflow questions.

Everything else is a massive undertaking in any project. In a similar situation, we've been slowly expanding the RxJava documentation beyond the docs in the source, but it is a lot, tedious and not the highest priority.