[SyntaxError: unable to resolve class rating] Movie Name (Year)

[DevXen]

So the Windows 10 version auto updated. and the thumbnails on lookup is awesome. however it broke something in my moving naming script.

it returns this when i match a movie: [SyntaxError: unable to resolve class rating] Movie Name (Year)

I checked my windows 7 version (running 4.8.5) and its still working find in that version.

I'm not sure what syntax format might have changed?


Thanks,
-Dev

[rednoah]

What is your format? Can your provide a minimal example the reproduces the issue?

[DevXen]

What is your format? Can your provide a minimal example the reproduces the issue?

i didn't include that cause my script is fairly big and complex. I'm not sure what part is causing the issue, i'd assume either the Critic rating or the content rating. but i'm not sure if its either of those parts. both of those are still working just fine on my TV episode Script though.

[rednoah]

There's literally nothing I can do unless you give me something to work with, other than guessing what code you might have written to see if I can reproduce the same issue.

[DevXen]

Ok i found the issue it is the critic rating.

Code: Select all

{" ["+(rating)+"★]"}

was that changed?

it appears if i change it to:

Code: Select all

{" ["+rating+"★]"}

it'll work though. hmm. strange.

[rednoah]

No idea. Groovy 3 has a new parser, so everything is different, so there'll be countless random differences, none of which matter, unless you do things that nobody else is doing, because it's all tested on many large scale code bases, which means none of those large scale code bases use this string+(var)+string construct you came up with. So you've got something unique coding style there.

[DevXen]

hey that's worked for the past few years. i'm not sure why i ended up doing that. coding too quick i guess. and it actually working i guess. weird. anyways. it's fixed. thanks =]

[rednoah]

hey that's worked for the past few years

Well, it looks like it should work, and it might work again in the future if somebody reports this bug to the Groovy developers, so they can fix it and add a test case.