Skip to content

Conversation

@mgol
Copy link
Member

@mgol mgol commented Apr 17, 2019

Summary

The camelCase implementation used by the data module no longer turns -ms-foo
into msFoo but to MsFoo now. This is because data is supposed to be
a generic utility not specifically bound to CSS use cases.

Fixes gh-3355

+2 bytes

Checklist

@mgol mgol added the Data label Apr 17, 2019
@mgol mgol added this to the 4.0.0 milestone Apr 17, 2019
@mgol mgol self-assigned this Apr 17, 2019
Copy link
Member

@dmethvin dmethvin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has this been a problem in practice? For complete consistency I'm okay with it and +2 bytes is a small price to pay.

The camelCase implementation used by the data module no longer turns `-ms-foo`
into `msFoo` but to `MsFoo` now. This is because `data` is supposed to be
a generic utility not specifically bound to CSS use cases.

Fixes jquerygh-3355
@mgol mgol force-pushed the camelCase-separation branch from 821d23f to fe1db84 Compare April 23, 2019 21:13
Copy link
Member

@gibson042 gibson042 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏

@mgol mgol removed the Needs review label Apr 29, 2019
@mgol mgol merged commit 8fae212 into jquery:master Apr 29, 2019
@mgol mgol deleted the camelCase-separation branch April 29, 2019 19:06
@lock lock bot locked as resolved and limited conversation to collaborators Oct 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Development

Successfully merging this pull request may close these issues.

Separate camelCasing logic between Data & CSS

4 participants