Update both instances from length to size

[Hassanelashram]

Fixes #8408

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

• PR is descriptively titled 📑 and links the original issue above 🔗
• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with rake test
• code is in uniquely-named feature branch and has no merge conflicts 📁
• screenshots/GIFs are attached 📎 in case of UI updation
• ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

Thanks!

[gitpod-io]

[Hassanelashram]

@Tlazypanda I made the changes here, could you please assign yourself as a reviewer as i can't?

also, I did not change the first instance of .length to .size as it was in a JS script tag and was not sure.

[codecov]

Codecov Report

Merging #8412 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #8412   +/-   ##
=======================================
  Coverage   81.89%   81.89%           
=======================================
  Files         101      101           
  Lines        5900     5900           
=======================================
  Hits         4832     4832           
  Misses       1068     1068           

[Tlazypanda]

Hey @Hassanelashram LGTM 🎉

[Hassanelashram]

@Tlazypanda Awesome, so that's it right ? You guys will take care of the merging ?

[Tlazypanda]

Yeah @Hassanelashram the maintainers will merge it when they are available next 😅 In the meantime feel free to dig deeper into the codebase or find other issues to work on ✌️ Welcome to Public Lab 🎈

[cesswairimu]

Hi @Hassanelashram, we encourage contributors to take one first-timer-only issue( These are issues with that label) and leave the others for new contributors coming in. Since this PR is ready, I would suggest we merge this PR and close #8402 to give another new contributor a chance to work on that. How does this sound? Thanks

[cesswairimu]

Merging this and closing the other one. Thanks all

[welcome]

Congrats on merging your first pull request! 🙌🎉⚡️
Your code will likely be published to PublicLab.org in the next few days, but first it will be published to https://stable.publiclab.org/ (it will take some minutes for this to load, and until then you may see logs from the build process). Please test out your work on this testing server and report back with a comment that all has gone well!
Do join our weekly check-in to share your this week goal and the awesome work you did 😃. Please find the link pinned in the issue section 📝
Now that you've completed this, you can help someone else take their first step!
Reach out to someone else working on theirs on Public Lab's code welcome page (where you'll now be featured as a recent contributor!). Thanks!

Help others take their first step

Now that you've merged your first pull request, you're the perfect person to help someone else out with this challenging first step. 🙌

https://code.publiclab.org

Try looking at this list of `first-timers-only` issues, and see if someone else is waiting for feedback, or even stuck! 😕

People often get stuck at the same steps, so you might be able to help someone get unstuck, or help lead them to some documentation that'd help. Reach out and be encouraging and friendly! 😄 🎉

Read about how to help support another newcomer here, or find other ways to offer mutual support here.

[jywarren]

Thanks @Hassanelashram @Tlazypanda @cesswairimu !!! 🎉

[Hassanelashram]

Thanks @Hassanelashram @Tlazypanda @cesswairimu !!! 🎉

@jywarren Pleasure! Hope I can be more helpful ehe 🤗