Skip to content
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

UNQUOTED_STRUCT_KEY only reported for implicit declaration #405

Closed
KamasamaK opened this issue Aug 4, 2017 · 0 comments
Closed

UNQUOTED_STRUCT_KEY only reported for implicit declaration #405

KamasamaK opened this issue Aug 4, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@KamasamaK
Copy link
Collaborator

This rule is not triggered when using dot notation to declare a new key.

Reported:

<cfset sampleStruct = {
    aKey="aValue",
    anotherKey="anotherValue"
}>

Unreported:
<cfset sampleStruct.yetAnotherKey = "yetAnotherValue">

It should be consistent and report both, recommending using array-notation when declaring new keys on a struct.

@TheRealAgentK TheRealAgentK added this to the 1.3.0 milestone Aug 12, 2017
@ryaneberly ryaneberly self-assigned this Aug 21, 2017
ryaneberly added a commit that referenced this issue Aug 21, 2017
ryaneberly added a commit that referenced this issue Aug 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants