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

removed text-transform from variable name #5296

Merged
merged 1 commit into from Mar 13, 2020

Conversation

shabith
Copy link
Contributor

@shabith shabith commented Feb 22, 2020

Description of what you did:

Hello There!
I was following the tutorial and realize that variable names are capitalized, which is a bit misleading.
So thought of removing that.

image

@codecov
Copy link

codecov bot commented Feb 22, 2020

Codecov Report

Merging #5296 into master will not change coverage by %.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #5296   +/-   ##
=======================================
  Coverage   13.71%   13.71%           
=======================================
  Files         633      633           
  Lines        8685     8685           
  Branches     1337     1337           
=======================================
  Hits         1191     1191           
  Misses       6319     6319           
  Partials     1175     1175           
Flag Coverage Δ
#front 11.67% <0.00%> (ø) ⬆️
#unit 38.42% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c05dcec...ac996ca. Read the comment docs.

@alexandrebodin
Copy link
Member

alexandrebodin commented Feb 25, 2020

Really think this should be merged :)

We are just waiting for some discussion in the team ;)

@soupette
Copy link
Contributor

I completely agree this should be merged it's really confusing to have a different casing than the one the user sets!

@soupette
Copy link
Contributor

@Aurelsicoko can you jump in on this?

@Aurelsicoko
Copy link
Member

Yes, let's do it! We should not modify the way the developer named the fields. We should not lowercase, or camelcase, or anything. Let things as they are ;)

LGTM

Copy link
Member

@alexandrebodin alexandrebodin left a comment

Choose a reason for hiding this comment

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

LGTM :) Thanks !

@alexandrebodin alexandrebodin added source: core:content-type-builder Source is core/content-type-builder package issue: enhancement Issue suggesting an enhancement to an existing feature labels Mar 13, 2020
@alexandrebodin alexandrebodin added this to the 3.0.0-beta.19.4 milestone Mar 13, 2020
@alexandrebodin alexandrebodin merged commit fe19bcb into strapi:master Mar 13, 2020
@shabith
Copy link
Contributor Author

shabith commented Mar 14, 2020

Thanks guys :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: enhancement Issue suggesting an enhancement to an existing feature source: core:content-type-builder Source is core/content-type-builder package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants