Interactive rating component using HTML, SASS, JS and Parcel

Community feedback

• 

  turtlecrab•550

  @turtlecrab

  Posted about 3 years ago

  Hey, it's very easy to make radio labels react to checked state without any js, just put inputs and labels side by side, input then label, and use + css selector like that: input:checked + label {...}. That's how I did it in this challenge following BEM class naming convention:

  .card__radio:checked + .card__radio-label {
    background: $primary;
    color: $white;
  }
  

  If you put inputs inside labels I think there is no easy way to achieve this, as far as I know there is no way to get a parent css selector from the child, and we need to bind our label selector to :checked pseudo-class of an input(maybe I'm wrong and there is a way, but there are no reasons to make it harder). The only thing you'll have to add is for attribute for the label like this: <label for="input-id"... so a label knows which input to check on click.

  About your javascript code which handles class toggles - it's not needed if we rewrite our layout as shown above, but as it's written I have a feedback. There are 5 almost identical functions that handle label clicks. If you haven't read about DRY programming principle yet (which stands for don't repeat yourself), then google it, it's the first principle we should be learning about. Here we can safely instead of 5 functions write just one:

  function handleRadChange(number){
      EnableButtonResetColours();
      document.getElementById("circle-" + number).classList.add("select-circle-clicked");
  }
  

  And html:

  <label id="circle-1" onclick="handleRadChange(1)" ... >
  <label id="circle-2" onclick="handleRadChange(2)" ... >
  ...
  

  The code is much simpler and if you decide to add some other functionality you'll have to add it to one place and not 5.

  So looking for duplicate code is good and we should do it and try to remove duplication when it's making sense. But if you are a beginner don't go crazy about it, start with just noticing duplicate code and do nothing about it. Then maybe when it's really similar like in the example above start trying to refactor it if you are feeling like it. If you are not, don't bother and leave it duplicated, it's totally fine at this stage. And sometimes it's just better to leave duplicate code(see here and here)

  Also you should add node_modules directory into your .gitignore file, as well as parcel related directories: .parcel-cache and dist. Just write them 1 directory per line. These are not supposed to be a part of git repository and .gitignore is where we list such files/dirs.

  If there are issues with deploying to Github Pages, try Vercel - I use it and it's just couple of clicks to add a repository and build it. I think with Vercel you don't even need to write a build script, it detects parcel automatically. Another choice is Netlify.

  11

  Marked as helpful
• 

  Danilo Blas•6,300

  @Sdann26

  Posted about 3 years ago

  Hi Juno!

  Recommendations I would make

  1. Use transitions, because it is aesthetically more pleasant to generate that transition effect when clicking or passing the cursor over an element like this, for example: To the class select-circle add transition: all 200ms to the class select-circle add transition: all 200ms.
  2. To the button with the text SUBMIT add letter-spacing: 2.5px this allows that the letters are separated the amount depends on what you believe convenient but in the design this way.
  3. To the div with the class attribution change it to <footer class="attribution"> since it is outside the main but it is inside the body and it is considered one more section of the page.
  4. To the images always add the alt attribute even if it is empty, if it is empty also add the attribute aria-hidden="true". In the first case is that if they are relevant images you add an alternative text and in the second case for accessibility issues you are mentioning that this image is more of an ornament that is why the aria-hidden.

  Otherwise as far as I have reviewed it seems to me that you have done a good project, the design is really good, there is always one or another thing that we do not know but we are investigating or we are warned that we are missing so go ahead, the last two points I mention are for the report, I recommend you always review the report that generates you frontend mentor to clean the errors and generate a new one without these.

  Without anything else to say good luck and keep it up.

  11

  Marked as helpful