Closed mglukhovsky closed 8 years ago
users
collection manually.This is a good idea for a document. @mlucy and @danielmewes are listing actual limitations, but @mglukhovsky is really offering a list of questions that I'll need answers to, though.
We talked about this a little bit yesterday, and it seems that the page really needs to cover two different things. One is "Limitations of current features" and the other is "Features that don't exist yet, but are planned".
GraphQL support, pagination, local user/password authentication: we don't have any of these, right?
Right, those would be "planned features".
Browsers supported by the client: do we have a known minimum?
I don't think we do, though there are some known issues with Internet Explorer 10 and 11 (see https://github.com/rethinkdb/horizon/issues/566 ). We could say something along the lines of us not having tested compatibility with older browsers extensively yet, and mention the known incompatibility. @deontologician do you know more about which browsers should work?
Environment versions
I'm not entirely sure what @mglukhovsky had in mind here, though one thing that would fit into this point are supported versions of npm and node. I don't think this is something we need to mention on this page though, since we don't have any ambition to add support for older npm or node version. Another thing that might be worth mentioning on this page is that setting up a Horizon server on Windows is still not as well tested.
Reconnection logic
Yeah, this is another one of the missing features. No automatic reconnection logic, and also if you do reconnect manually, any active subscriptions will not (yet) automatically resume and will have to be set up again from scratch on the client.
I am not sure which browsers should work. We know for certain it doesn't work on mobile safari, and it seems IE 10 based on @danielmewes testing. We have polyfills for the most bleeding edge stuff, but if your browser doesn't support Promises directly, you'll need to add your own polyfill
We should add a document outlining some current limitations in the server, and certain operations (as well as temporary workarounds as features get added). For example:
Other suggestions are welcome.