-
Notifications
You must be signed in to change notification settings - Fork 1
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
[next] rename /hoodie/bundle.js route to /hoodie/client.js #89
Comments
Sounds good to me, it make sense even if it's not a 1:1. |
Makes sense to keep it in sync with the current documentation, especially since "bundle" sounds a lot more related to Browserify than Hoodie. 1:1 FTW. 👍 |
+1
Currently it is the pre-built hoodie-client though. |
it’s decided then, let’s do it: hoodiehq/hoodie-server#459 |
hoodiehq/discussion#89 * * * This commit was sponsored by Neighbourhoodie You can hire Neighbourhoodie for all your Hoodie / CouchDB / Offline First needs http://go.hood.ie/thehoodiefirm
hoodiehq/discussion#89 * * * This commit was sponsored by Neighbourhoodie You can hire Neighbourhoodie for all your Hoodie / CouchDB / Offline First needs http://go.hood.ie/thehoodiefirm
hoodiehq/discussion#89 * * * This commit was sponsored by Neighbourhoodie You can hire Neighbourhoodie for all your Hoodie / CouchDB / Offline First needs http://go.hood.ie/thehoodiefirm
We talk about about "Hoodie client" and it will be mentioned a lot in the documentation, also the main repository is
hoodie-client
. So it would be more consistent to have the route where the Hoodie client is served/hoodie/client.js
.Note that
/hoodie/client.js
is not servinghoodie-client
1:1.hoodie-client
returns a Hoodie constructor,/hoodie/client.js
returns an instance of Hoodie with options passed in.Any thoughts?
@boennemann @christophwitzko @janl
The text was updated successfully, but these errors were encountered: