- fork this repository
- create a new branch named
lab01-; +<your name>e.g.lab06-amanda - write your code
- push to your repository
- submit a pull request to this repository
- submit a link to your PR in canvas
- Include a Readme.md (contents described below)
- Create a custom generic list for an e-commerce store to hold an inventory of products
- Include an enum in your Product (i.e. ProductType)
- Make sure the generic has the functionality to use a foreach loop.
- Your generic collection should include
Add(),Remove()items in the collection - Make it so you can
ViewAlland create a method to output all items to the console - Add at least 10 items to your List, and output them to the console.
- Add some items through the
Add()Method, and others through a collection initializer
- Add some items through the
- include an AtIndexOf method in your collection. Have it return the index of that item in the Collection.
A README is a module consumer's first -- and maybe only -- look into your creation. The consumer wants a module to fulfill their need, so you must explain exactly what need your module fills, and how effectively it does so.
Your job is to
- tell them what it is (with context)
- show them what it looks like in action
- show them how they use it
- tell them any other relevant details
This is your job. It's up to the module creator to prove that their work is a shining gem in the sea of slipshod modules. Since so many developers' eyes will find their way to your README before anything else, quality here is your public-facing measure of your work.
Refer to the sample-README in the class repo for an example.
-
7pts: Program meets all requirements described in Lab directions
-
3pts: Code meets industry standards
-
Readme.md required for submission. Missing readme document and tests will result in a best score of 2/10
