missing name after . operator
See original GitHub issueDescribe the bug
Since the last upgrade to 19.0.2 we can’t access any clients configured in the realm. Page displays the error:
missing name after . operator
Unfortunately there are no logs from the keycloak pod to narrow down the problem
Version
19.0.2
Expected behavior
To be able to edit/update configured clients
Actual behavior
How to Reproduce?
not sure how to reproduce this behavior
Anything else?
Another instance of KC 19.0.2 has a similar error:
missing ) after argument list
No response
Issue Analytics
- State:
- Created a year ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
SyntaxError: missing name after . operator - JavaScript | MDN
The JavaScript exception "missing name after . operator" occurs when there is a problem with how the dot operator ( . ) is...
Read more >JavaScript SyntaxError - Missing name after . operator
This JavaScript exception missing name after . operator occurs if the dot operator (.) is used in the wrong manner for property access....
Read more >JavaScript Error, Missing Name After . Operator
Try changing it to an indexer. document.getElementById(parent["span"+i]);.
Read more >How to Fix a 'Missing Name After . Operator' Error in a Script
The error occurs when you use dot walking to access a table field whose name is a reserved word in JavaScript. For example,...
Read more >SyntaxError: missing name after . operator
The dot operator ( . ) is used for property access. You will have to specify the name of the property that you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Perhaps we have already fixed this issue. @chuegel could you try testing this in a nightly version?
Thanks for verifying @chuegel!