I planned to do the following things in Week 1 and 2 -
Improving the existing generator.
Removing bugs from the Yeoman generator.
Adding unit tests and e2e tests for the existing generator.
Improving the tutorial for using the Yeoman generator.
Adding initial features for creating new components (question to ask whether the user wants to create a new component or old component and follow-ups)
I already updated the tutorial once and I would like to start early by adding tests (unit and e2e) for the existing generator. There are already some tests that check linting. I will search and read about various alternative we can use for tests (Yeoman-test, Jest, Mocha) and complete writing tests in 3 days hopefully. :smile:
That's my plan. Any suggestions are welcome. :smiley:
that sounds great!
biojs/generator-biojs-webcomponents#10 - I sent a PR to change generator's name from "@biojs/generator-biojs-webcomponents" to "generator-biojs-webcomponents" since the criteria for a generator to appear in Yeoman's registry is that the name should begin with "generator-".
Hey Yo, I’ve asked Nikhil to write an introductory blog at biojs.github.io Can you review it once (and suggest other things which we can include if needed)?
I think Yo has already merged the PR. Just a suggestion: try giving meaningful names to the branches too. It’s a good practice. For instance, if the branch is dedicated to updating dependencies, just give it a name update-dep or update-dependencies.
About the bug - The logic for converting a string to camel case was wrong due to a silly mistake of me, this fixes that.
This image contains two new tests I wrote. I think these are sufficient considering the features we have now. If I have forgotten some test cases, please let me know. These will pass after the previous on Travis CI after the previous PR fixing the bug will be merged. I have tested them locally, all of the tests passed.