You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to compile the i18next library but got a compilation error. [error] Message Phase1ReadTypescript.scala:72 Failed to parse: Parse error at 286.11 ''>'' expected but identifier key found [file => ../i18next/typescript/t.d.ts, thread => 527, project = > birl-web, ms => 10553, phase => typescript, id => i18next]com.olvind.logging.Logger$LoggedException: Failed to parse: Parse error at 286.11 ''>'' expected but identifier key found [error] at com.olvind.logging.Logger$LoggingOps$.fatal$extension(Logger.scala:178)
Here is an image of the affected code:
I also prepared some minimalistic examples to demonstrate the problem: st-error-demo.zip
Hi @JurajBurian ,
I’ve created this PR with a test case that reproduces the issue. I’m not sure I can fully resolve it, but I wanted to submit the PR as an initial attempt. Hopefully, it serves as a starting point for others familiar with the project to jump in and work on a solution.
I tried to compile the i18next library but got a compilation error.
[error] Message Phase1ReadTypescript.scala:72 Failed to parse: Parse error at 286.11 ''>'' expected but identifier key found [file => ../i18next/typescript/t.d.ts, thread => 527, project = > birl-web, ms => 10553, phase => typescript, id => i18next]com.olvind.logging.Logger$LoggedException: Failed to parse: Parse error at 286.11 ''>'' expected but identifier key found [error] at com.olvind.logging.Logger$LoggingOps$.fatal$extension(Logger.scala:178)
Here is an image of the affected code:
I also prepared some minimalistic examples to demonstrate the problem:
st-error-demo.zip
maybe it's the same issue as #633
Please comment your opinion folks.
Thank you very much
p.s. you are doing an amazing job!
The text was updated successfully, but these errors were encountered: