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

camelCase JavaScript Asset Filenames #9140

Closed
55 tasks done
noi5e opened this issue Feb 6, 2021 · 4 comments
Closed
55 tasks done

camelCase JavaScript Asset Filenames #9140

noi5e opened this issue Feb 6, 2021 · 4 comments
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration fto-candidate issues which are meant to be solved by first timers but aren't well-formatted yet

Comments

@noi5e
Copy link
Contributor

noi5e commented Feb 6, 2021

See this comment thread.

Some of the JS assets use camelCase naming convention, while others use underscore_filename convention:
106628319-b9adcf00-658a-11eb-8af8-c780e5bcdc57

Let's standardize them and use camelCase since that's the JS way! These make great first-timer-only issues. (I definitely welcome help in making these!)

Don't forget to do a search in your IDE for wherever the file is required. For example, some of these are loaded in config/initializers/assets.rb.

Completed

🔬 Needs Further Research

  • simple-data-grapher.js
    • This seems to be one of Public Lab's own external packages that we require in package.json?
    • May not be so easy to change this one, or out-of-scope for an FTO.
@larabee7777
Copy link
Contributor

Hi do you need help here?

@noi5e
Copy link
Contributor Author

noi5e commented Feb 18, 2021

@larabee7777 You've already completed one of these first-timer-only issues (#9148). I think generally each person gets only one FTO issue.

If you're looking for another way to contribute, you could browse through our help wanted issues. OR you could also help someone else get through their own FTO issue. maybe the two open issues above? You could leave a comment there seeing if they need any help.

You can also make your own FTO issue. We have a bunch of first-timer-only candidate issues that need to be broken down and formatted into FTO issues.

@larabee7777
Copy link
Contributor

@larabee7777 You've already completed one of these first-timer-only issues (#9148). I think generally each person gets only one FTO issue.

If you're looking for another way to contribute, you could browse through our help wanted issues. OR you could also help someone else get through their own FTO issue. maybe the two open issues above? You could leave a comment there seeing if they need any help.

You can also make your own FTO issue. We have a bunch of first-timer-only candidate issues that need to be broken down and formatted into FTO issues.

Ah ok I see thanks so much I will check out the other issues :)

@noi5e
Copy link
Contributor Author

noi5e commented Feb 23, 2021

Okay, I think with the two PRs that got merged today, we can close this issue!!! Thanks to everyone who made their first PRs and helped us with this! @Hari-tn67 @katiebankhead @shadowoflight @manchere @StellaWanja @redwan-mahmud @larabee7777 @akshay4n @ghostoverflow @StreakSharn @Nagsenwaghmare 🏆 🎉 🍾

If any of you would like to help out some more, or get more experience in open source, check out https://code.publiclab.org/. Feel free to check out our help wanted issues, create your own first-timer-only issue, do code review... You can also ask for help setting up plots2 locally, try to find bugs, or write issues. And if you haven't checked us out on Gitter, please do!

@noi5e noi5e closed this as completed Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration fto-candidate issues which are meant to be solved by first timers but aren't well-formatted yet
Projects
None yet
Development

No branches or pull requests

2 participants