Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"Unexpected token. Expected one of: ." at line 225
See original GitHub issueHere is my schema.prisma,
It was base on prisma 1.34, introspected by prisma2 init.
I took hours to try my best to fix the grammer error.
But the vscode still tell me : “Unexpected token. Expected one of: .” at line 225
Same error when I execute prisma2 generate.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Re: Unexpected token: '<=', expected one of - Qlik Community
This is a fairly generic message which typically suggests something is wrong with the contents of one of your variables. Given that it...
Read more >Parsing Error: Unexpected token, expect ",": Stateless ...
I'm using a stateless functional component to draw a graph, the data for the graph will be passed down via props inside of...
Read more >unexpected token '<', "<!doctype "... is not valid json - You.com
It looks like your PHP script is not returning JSON but rather a rendered HTML doc. The error you noted Uncaught (in promise)...
Read more >DB2 for IBM i: Listing of SQL messages
Message Text: An XPath expression has an unexpected token &1 following &2. ... result contains more than one atomic value and a singleton...
Read more >Unexpected Token error when attempting to test a Test Class
QueryException: unexpected token: WHERE Stack Trace Class.MyClosedIssuesTest.testMyClosedIssues: line 23, column 1
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 Free
Top 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
I figure out that the Multiple-Reference Relationships are not necessarily making field name equals to name in @relation(name) . I think the spec is misleading, besides, a foreign key usually named like “FK_TABLENAME_xxx” rather than field name.
@pantharshit00 closing issue, please check them out, thanks.