tech-student-labs/cnd_cotton_factory_exercise

Class team project to develop a Spring Web microservice

cnd_cotton_factory_exercise's Issues

Sweater Product Details

Please do some research to add Sweaters to our product line. There's many kinds of sweaters so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Sweater
    type: String
    sleeve: Integer
    neck: Integer
    chest: Integer
    size: String
    customSize: String (read only representation of chest x neck x sleeve)
    color: String
    longSleeve: Boolean
    price: BigDecimal

Restrictions

• Sweaters come in the following types: cardigan, pullover, turtle neck, vest
• Sweaters must either have a size or they must have sleeve, chest and neck measurements, but not both.

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Sweater data as JSON
• Should not include sleeve, chest or neck measurements; only size or customSize

Accessories Product Details

Please do some research to add accessories to our product line. There's many kinds of accessories: socks, scarves, cuff links, etc. So please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Accessory
    type: String
    size: Integer
    material: String
    designer: String
    color: String
    price: BigDecimal

Requirements

• come in the following types: belt, socks, scarf, cuff link, tie clip
• can be these materials: cotton, silk, leather, metal
• designer options: Encoded, Footsy, Stepper Leper

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open so you can use it on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Accessorie data as JSON

Pants Product Details

Please do some research to add Pants to our product line. There's many kinds of Pants so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Pants
    type: String
    inseam: Integer
    waist: Integer
    size: String (read only representation of waist x inseam)
    color: String
    designer: String
    price: BigDecimal

Pants come in the following types: athletic, jeans, culottes, dungarees.
The top designers are: Encoded, Jeanery, Trouser Wouser.

This work may include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This will require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests accept JSON

Responses:

• Pants data as JSON
• Should not include inseam or waist measurements.

Dress Product Detail

Please do some research to add Dresses to our product line. There's many kinds of dresses so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Dress
    type: String
    waistSize: Integer
    hipSize: Integer
    length: Integer
    size: String
    customSize: String (read only representation of waist x length)
    color: String
    price: BigDecimal

Restrictions

• Dresses come in the following types: tunic, gown, wrap, tutu and only dress shirts can have sleeve and neck measurements.
• Dresses must either have a size OR they must have waist, length and hip measurements, but not both.

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Dress data as JSON
• Should not include sleeve or neck measurements; only customSize.

Jacket Product Details

Please do some research to add Jackets our product line. There's many kinds of shirts so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Jacket
    season: String
    size: String
    color: String
    style: String
    adultSize: Boolean 
    price: BigDecimal

Requirements

• Jackets are chosen by season only: winter, spring, summer, fall.
• They come in these styles only: denim, hooded, overcoat, bomber
• Valid sizes: small, medium, large, extra large

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Jacket data as JSON

Slacks Product Details

Please do some research to add Slacks to our product line. There's many kinds of Slacks so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Slacks
    type: String
    inseam: Integer
    waist: Integer
    size: String (read only representation of waist x inseam)
    color: String
    designer: String
    price: BigDecimal

• Slacks come in the following types: casual, formal.
• The top designers are: Encoded, Slick, Trouser Wouser.

This work may include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This will require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Slacks data as JSON
• Should not include inseam or waist measurements.

Shirts Product Details

Please do some research to add Shirts to our product line. There's many kinds of shirts so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Shirt
    type: String
    sleeve: Integer
    neck: Integer
    size: String
    customSize: String (read only representation of neck x sleeve)
    color: String
    longSleeve: Boolean
    price: BigDecimal

Restrictions

• Shirts come in the following types: tee, dress, polo, henley and only dress shirts can have sleeve and neck measurements.
• Shirts must either have a size or they must have sleeve and neck measurements, but not both.

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Response

• Shirt data as JSON
• Should not include sleeve or neck measurements; only size or customSize

Skirts Product Details

Please do some research to add Skirts to our product line. There's many kinds of Skirts so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Skirt
    type: String
    waistSize: Integer
    length: Integer
    size: String
    customSize: String (read only representation of waist x length)
    color: String
    price: BigDecimal

Restrictions

• Skirts come in the following types: layered, wrap, mini.
• Skirts must either have a size OR they must have waist and length measurements, but not both.

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open for use on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

SPECS

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests accept JSON

Responses:

• Dress data as JSON
• Should not include waist or hip measurements; only customSize.

Tie Product Details

Please do some research to add accessories to our product line. There's many kinds of accessories so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Tie
    type: String
    length: Integer 
    width: Integer
    material: String
    designer: String
    color: String
    price: BigDecimal

Requirements

• come in the following types: bow tie, neck tie
• can be these materials: cotton, silk, nylon
• designer options: Encoded, Footsy, Stepper Leper

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open so you can use it on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Tie data as JSON

Shoes Product Details

Please do some research to add Shoes to our product line. There's many kinds of shoes so please use your best judgement to implement a solution that doesn't require adding a bunch of models.

Shoe
    size: Integer
    height: String
    type: String
    material: String
    designer: String
    laced: Boolean
    price: BigDecimal

Requirements

• come in the following types: heels, athletic, boot, sandal
• come in the following heights: normal, ankle, knee
• can be these materials: canvas, leather, rubber
• designer options: Encoded, Footsy, Stepper Leper

This work will probably include:

• Entities
• Repositories
• Services
• Controllers

All code must be 100% tested. This might require more than one PR so keep this issue open so you can use it on each PR dedicated to this feature.

All questions and concerns should be discussed here before any code is submitted. After code is submitted use the relevant PR to discuss the implementation.

Specs

URI	HTTP Request	REST Method	Response	Description
/api/products/{product_name}	GET	List	200 OK	A listing of all available products.
/api/products/{product_name}	POST	Create	201 CREATED	Create a new product.
/api/products/{product_name}/{productId}	GET	Read	200 OK	Details for a specific product.
/api/products/{product_name}/{productId}	PUT	Update	200 OK	Update a specific product.
/api/products/{product_name}/{productId}	PATCH	Update	200 OK	Partially update a specific product.
/api/products/{product_name}/{productId}	DELETE	Delete	204 NO CONTENT	Delete a specific product.

Requests: JSON

Responses:

• Shoe data as JSON