frasersgroup / schemas Goto Github PK

Add to private-schemas

How do we handle this difference in our schema? Are Product entities at the Style or SKU level? Can see a few approaches at the moment:

1. Style-Level Products including SKUs - The big pro to me here is that all the information is saved at the style level and not repeated for it's x SKUs. In this design SKUs are saved as a collection on the Style Level Product.

2. SKU-Level Products - All information is saved at the SKU level. Looking at the Style level requires a query or aggregate where Style ID = Style ID. Downside - editing style-level info must be saved to each individual SKU.

3. Both! We create a Style and a Product and they have a relationship. A Style has many Products. Downside is now we have 2 entities to deal with vs 1. Did we overcomplicate, or is this a good model of the domain?

Personally I'm a fan of 1 or 3.

Need to publish the schemas as an npm package for importing into highstreet

SD has a specific SD SKU

Do we use UPCs?

Likely a json schema -> markdown converter. Should already exist and be pretty simple to generate

See comment in #8

Based on Category?

We need a way to compile the schemas to a single object by dereferencing the $ref'ed fields.

Likely a good reference: https://www.npmjs.com/package/json-schema-ref-parser

Need to fill out the rest of the top-level schemas for:

• Product
• Account
• Role