Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

[Bug] Use camelcase in prop names #254

Closed
1 task
dhruvkb opened this issue Sep 22, 2021 · 5 comments · Fixed by #262
Closed
1 task

[Bug] Use camelcase in prop names #254

dhruvkb opened this issue Sep 22, 2021 · 5 comments · Fixed by #262
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed
Projects

Comments

@dhruvkb
Copy link
Member

dhruvkb commented Sep 22, 2021

Description

These components use the string 'URL' in the prop name.




openverseLicenseURL: String,

This leads to the following syntax where the component is used with props:

<Component :something-something-u-r-l="value"/>

This is not looking good. Changing the props from 'URL' to 'Url' would fix this.

Resolution

  • 🙋 I would be interested in resolving this bug.
@dhruvkb dhruvkb added good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🛠 goal: fix Bug fix 💻 aspect: code Concerns the software code in the repository labels Sep 22, 2021
@dhruvkb dhruvkb added this to Backlog in Openverse Sep 22, 2021
@theshakeabhi
Copy link
Contributor

I have been going through the code in the main and I found these:
ccLicenseURL has been used 20 times in 9 different files
licenseURL has been used 14 times in 5 different files
openverseLicenseURL has not been used till now.

Should one changes every occurance of it?

@krysal
Copy link
Member

krysal commented Sep 23, 2021

@theshakeabhi that is correct, it should be changed in all places to keep uniformity. Contributions to this are very welcome!

@theshakeabhi
Copy link
Contributor

theshakeabhi commented Sep 24, 2021

@krysal, these changes that @dhruvkb mentioned is on a specific branch https://github.com/WordPress/openverse-frontend/tree/428be354eada6b29dc3d63f21c7960e42386b423. So should I pull this branch and make this as base branch and make modification or should I take the main branch as the base branch?

@dhruvkb
Copy link
Member Author

dhruvkb commented Sep 24, 2021

@theshakeabhi Make the changes on main. I used the absolute commit hash so that the issue remains valid after the fix is pushed.

@theshakeabhi
Copy link
Contributor

@dhruvkb That's intresting. Thank you directing me.

@theshakeabhi theshakeabhi mentioned this issue Sep 24, 2021
7 tasks
@dhruvkb dhruvkb moved this from Backlog to In progress in Openverse Sep 24, 2021
Openverse automation moved this from In progress to Done! Sep 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed
Projects
No open projects
Openverse
  
Done!
Development

Successfully merging a pull request may close this issue.

3 participants