ai on next
Update dev practices (compare)
dependabot[bot] on npm_and_yarn
ai on main
Bump ini from 1.3.5 to 1.3.7 (#… (compare)
dependabot[bot] on npm_and_yarn
Bump ini from 1.3.5 to 1.3.7 B… (compare)
ai on next
Fix branch name (compare)
ai on next
Update dependencies (compare)
ai on master
ai on main
ai on next
Typo (compare)
ai on next
Use resend shortcut (compare)
ai on next
Use nameless single job (compare)
ai on next
FIx job name (compare)
ai on next
Update dependencies Add cache to CI (compare)
ai on next
Fix workflow format (compare)
ai on next
Clean up GitHub Action config (compare)
ai on next
Add 0/clean action docs (compare)
ai on next
Simplify docs Simplify another example (compare)
quick question.
On a Java Sever using Logux Proxy:
Token is not sent with all Actions, only with Auth command once?
When Proxy calls our stateless Rest Backend with an Action (like subscribe, or custom action) how do we know the authentication took place fine?
ps: I'm using Logux Vuex, do I need to manually add the token to each commit.sync( call?
but what about the subscribe, which is done automatically from the loguxMixin
Hello, basic usecase (Logux Vuex, Logux Proxy, Java Spring Boot Rest Backend):
ps: I know that a better approach would have been to set the UUID in Vuex, so the RESEND action would have taken care of all this,
but is there a best practice for my scenario?
isSubscribing
key, but it's key to wait when an application will connect to a some channel
the client terminal tab says:
```Compiled successfully!
You can now view client-logux in the browser.
Local: http://localhost:3000
On Your Network: http://192.168.11.5:3000```
but nothing displays on the local address. It only displays on the 'on your network' address which seems odd too.
It would be great if logux/undo
included the failed action
that is being undone. I understand from https://logux.io/guide/concepts/action/#system-actions that:
action.id will be equal to meta.id of reverted action
however that means I need to keep a queue of added actions in order to find the id
and know what the action being undone was.
Or am I missing something here?
'logux/unsubscribe'
and then Client.changeUser( guestUserId, undefined )
.changeUser()
I get a "logux/subscribe"
with resubscribe: true
and the original user.dispatch.local()
looks like what you want. See: https://logux.io/recipes/cross-tab/
'login/done'
I assume client.changeUser( action.userId, action.token )
needs to called to change from anonymous
to the logged in user.logux/subscribe
the client
is in a incorrect state as it still has the anonymous
login which hasn't received alogux/sychronized
leaving setSynchronized()
in status()
never passing if (Object.keys(processing).length === 0)
because it has the anonymous
item still present. Apologies for the long winded explanation.client.destroy()
and then client.start()
with the logged in users credentials.
const Logux = createLogux({
subprotocol: config.subprotocol,
server: config.loguxProxy,
userId: someUserId
token: i-want-to-change-this-when-user-pushes-a-button
});
online
and has a log of updates to send to the server, how can I find out when they've all been sent. This is all handled y Logux client code and I can't see how to see what it is doing.Hey, guys! I try to build a simple app with rails backend but faild with this. The connection from client goes to proxy and rails well, but when I try to add something to logs proxy does not receive any message.
I suspect that client does not send action to server. What I did wrong? client send action code below
loguxClient.log.add({
type: 'question/pick',
payload
});
syncSince()
syncSince()
-> syncSinceQuery()
-> outFilter()
matches the "anonymous" signin log entry and discards the earlier unsent crud log items.