-
Notifications
You must be signed in to change notification settings - Fork 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
reactivex.io documentation needs to reference v5+ #2369
Comments
This issue is still present. How can we act on this and update the documentation? |
List of differences between reactivex.io documentation and the actual implementation:
There are more but it will take some time to compile. Does anyone know how we can remove these outdated entries from the documentation to avoid countless confusion and time wasted? |
May 2017 - Any update? |
@Karasuni I don't think providing the date is productive. |
But how can we resolve this issue? |
Hey, @niklas-wortmann, do you think you can have a look at the reactivex.io site? The git repo for it is here: https://github.com/ReactiveX/reactivex.github.io I can get you access, and put you in contact with the maintainers. I think we just need to get all of the RxJS stuff there to point to our documentation site. |
I will have a look and see what we can do about that! Thanks for mentioning me. I was absolutely not aware of this |
The docs on reactivex.io e.g. http://reactivex.io/documentation/operators/repeat.html still reference the v4 implementation API.
I'm not immediately sure how these docs are generated and more importantly, kept in sync with our real docs. I imagine @mattpodwysocki knows, so hopefully he can help lead the way.
If it's currently just manual process of updating their repo, I'm initially inclined to just remove them and/or link to our docs instead. It's not ideal, but I think it's better than having to continuously be told our docs on reactivex.io are out of date or not as good as our real docs (if they ever are actually good...)
The text was updated successfully, but these errors were encountered: