-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse error for numeric struct keys #599
Comments
Thanks. I did upgrade cfparser - I'll see what the issue is.
…On Mon, Oct 22, 2018 at 8:29 PM KamasamaK ***@***.***> wrote:
On the latest 1.5.0 build, I am getting PARSE_ERRORs on numeric struct
keys. This does not occur with 1.4.1. Here is an example.
<cfset var foo =
{
"0": "priority",
"5": "status",
"10": "name",
"15": "date",
"20": "category"
}
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#599>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFtZu7gcgPBImQBT4PG3ygUxtnEebnlCks5unmLNgaJpZM4X0cVZ>
.
|
updated cfparser again, seems to be working with the latest |
They're not getting PARSE_ERRORs anymore, but now they're getting PLUGIN_ERRORs. |
Thanks @KamasamaK . I tried it on the test ParseError\keys_599.cfm -- and don't see the issue. Can you help me duplicate it. |
I cannot reproduce it with your |
I've rebuilt today and it looks good good now. |
Thanks @KamasamaK
…On Mon, Sep 16, 2019 at 3:22 PM KamasamaK ***@***.***> wrote:
Closed #599 <#599>.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#599?email_source=notifications&email_token=ABNVTOZWHJPYELSEQQA53SDQJ7MFTA5CNFSM4F6RYVM2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTU2YFRA#event-2637529796>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNVTO7NENUXJ7GOKXL67VLQJ7MFTANCNFSM4F6RYVMQ>
.
|
On the latest 1.5.0 build, I am getting PARSE_ERRORs on numeric struct keys. This does not occur with 1.4.1.
Even worse, it does it for quoted struct keys, which is recommended in one of the rules.
Here is an example with both
The text was updated successfully, but these errors were encountered: