Always feel free to reach out if you have any issues 😄
Hi @DylanPiercey , is this the only way to trigger a page reload routed through rill rather than the server?
https://github.com/DylanPiercey/submit-form/blob/master/client/index.js#L30
https://github.com/DylanPiercey/submit-form/blob/master/client/index.js#L30
If you just want a reload you can do
ctx.go(ctx.req.href)
See the example from the readme:
// Here we listen for `keyup` events that match a `.verification-code` element.
delegate.on('keyup', '.verification-code', (ev, go) => {
// `currentTarget` will be the element that matched the selector.
const input = ev.currentTarget;
const code = input.value
// The second argument is the 'go' utility, which is much like native fetch but tells Rill to navigate.
if (code.length === 5) {
// In this case when we have 5 characters, we navigate to the submission page.
go('/submit', {
method: 'POST',
body: { code }
})
}
})
Also I was wrong, it's not 'ctx.go' it is passed in to event handlers.
One other thing to note though is that with @rill/delegate you need to bind the event handler for each request because all event handlers get reset (so that if you navigate to a new page it doesn't take all the old handlers). Let me know if that doesn't make sense.
Just curious, what module bundler are you using? Webpack/Browserify/Rollup/Lasso?
Or @rill/html?
Sorry, just trying to get an idea of how people are using Rill :).
Didn't know dust did client side rendering.
What are you doing when this happens?
Thanks, it looks like it can't find
ctx.req.original.socket.server within this:function delegate (options) {
return function delegateMiddleware (ctx, next) {
// Store reference to server for later.
_server = ctx.req.original.socket.server
// Clear all listeners.
for (var type in _listeners) _listeners[type] = []
// Continue request.
return next()
}
}
Because that should work as far as I can tell atm
Any reason you are tied to the old version?
I'd definitely recommend upgrading if possible.
If it's not possible quickly you can use the following patch.
const server = rill()
.use(({ req }, next) => {
req.original.socket.server = server
return next()
})
// Rest of middleware.
.use(...)
.listen()
Also FTR all 'breaking' changes of Rill since 2x have been because of @rill/http so unless you (or some of the middleware) are relying on @rill/http it won't be an issue.
And most of the middleware do not rely on @rill/http, delegate is a rare exception.