Add Part Diagram

[SomethingSexy]

• A part will be attached to a platform but stored independently
• Parts can be shared across platforms
• When adding a new part, it will get added to the database but won't be "activated" until the platform has been activated
• You would probably want to search for parts by platform. Although you could do independent part searching
• Parts can have other parts

How to organize parts?

Either hierarchical or maybe part group documents?

Flat parts document and then a hierarchy grouping? Be able to select multiple parts to group them into a new part? OR we just make parts completely flat, maybe you can group them for organization within the platform? When some adds an actual product it will link parts from a platform.

Properties

• name
• description
• type
• fields (additional configurable fields)
• createdPlatformId - the id of the platform it was originally created from

[SomethingSexy]

We will want to add a part to a driagram via api/platform/:id/part post.

Then we will take the id that gets generated and add it to the diagram parts array.

[SomethingSexy]

We will still need to figure out how to fetch the parts and put them in the proper state. We won't wantt fetch all parts just the ones for this platform.

Maybe when we fetch platform we will return both partIds and parts, then the reducers can handle it.