Service - Catalog Standard: Difference between revisions
Jump to navigation
Jump to search
(→Notes) |
(→Notes) |
||
| Line 30: | Line 30: | ||
: string | : string | ||
= | = Filter for each categoryTreeNode = | ||
* In most cases all categoryTreeNodes will share the same filter, matching the catalog's filter, but allow for each categoryTreeNode to set its own. When this happens it will likely add to the default filter, to maintain a standard experience for the user. | * In most cases all categoryTreeNodes will share the same filter, matching the catalog's filter, but allow for each categoryTreeNode to set its own. When this happens it will likely add to the default filter, to maintain a standard experience for the user. | ||
* When creating a new categoryTreeNode for a catalog the requiredData and filter for the node can be set, if not set the default is to inherit from that node's parent categoryTreeNode. If is a top level node it inherits from the catalog's (default) filter. | * When creating a new categoryTreeNode for a catalog the requiredData and filter for the node can be set, if not set the default is to inherit from that node's parent categoryTreeNode. If is a top level node it inherits from the catalog's (default) filter. | ||
* Not sure how to handle updating catalog's (default) filter, perhaps have a bool in the categoryTreeNode that sets whether it's filter should track and update when catalog filter updates. | |||
= Working documents = | = Working documents = | ||
Revision as of 11:06, 19 December 2020
Overview
Handler service for the standard catalog type.
Repository
https://bitbucket.org/stb_vit/catalog-standard/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configTag: "CatalogTreeServiceName"
configKey: {eg: "CatalogTreeServiceName"}
configValue: {eg: "CatalogTreeStandard"}
}
Catalog
Fields
- catalogId
- (partition key)
- filters
- string
Filter for each categoryTreeNode
- In most cases all categoryTreeNodes will share the same filter, matching the catalog's filter, but allow for each categoryTreeNode to set its own. When this happens it will likely add to the default filter, to maintain a standard experience for the user.
- When creating a new categoryTreeNode for a catalog the requiredData and filter for the node can be set, if not set the default is to inherit from that node's parent categoryTreeNode. If is a top level node it inherits from the catalog's (default) filter.
- Not sure how to handle updating catalog's (default) filter, perhaps have a bool in the categoryTreeNode that sets whether it's filter should track and update when catalog filter updates.