Editor.navigate not working

Troubleshooting
1

I’m not sure what the cause is but I recently had a sync conflict which I manually resolved (not sure if this is related but I have no idea why I’m in the situation I’m in currently), but now none of the editor.navigate commands I’m using in the Action Bar (e.g. editor.navigate({page="CONFIG"})) are working. When I inspect the Javascript console I see the following error:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'match')
    at xe (client.js?v=cache-1756492572351:41:22920)
    at lo (client.js?v=cache-1756492572351:41:22662)
    at editor.navigate [as callback] (client.js?v=cache-1756492572351:98:28307)
    at Lc.syscall (client.js?v=cache-1756492572351:42:32863)
    at Lc.localSyscall (client.js?v=cache-1756492572351:42:32464)
    at Lo.s [as fn] (client.js?v=cache-1756492572351:280:13048)
    at Lo.call (client.js?v=cache-1756492572351:102:50644)
    at G1 (client.js?v=cache-1756492572351:102:54572)
    at client.js?v=cache-1756492572351:102:42956
    at async T2 (client.js?v=cache-1756492572351:102:46641)

I’ve done a full reindex and system reload and I’m still having this issue. Everything else seems to work (editor.invokeCommand) and I don’t notice any other issues with queries or any other functionality.

Any suggestions?

2

This syntax isn’t recommended anymore. The new syntax is editor.navigate("CONFIG"). I forgot a case in handling the legacy support, which is why this now broke. Made a PR to fix that, although I’d recommend you switch to the new syntax as thats arguably cleaner.

3

Thank you @MrMugame ! I was going crazy wondering what had happened! I prefer the new syntax (but couldn’t get it to work previously), glad to see it works now! :saluting_face: