Open zccz14 opened 4 months ago
Some additional points. Using a tree-structured resource management model involves more than just concatenating datasource_id
and product_id
together. For instance:
encodePath
, decodePath
with standard posix-style path libraries (in browser environments, these libraries can be used by configuring the packager, and the same consideration should be given when packaging plugins as IIFE).provideTicks
.decodePath
within provideDataSeries
.GSR
into two fields, should it be directly merged into the IProduct
interface? Or has it become meaningless altogether?We will never again seek to impose any requirements on the path format of product_id
.
We will never demand to extract any structured information from the hierarchical path of product_id
.
Therefore, the specific structure within the product_id
path is no longer important; what matters is:
Describe the feature
Make all product ID unique for global.
Embed datasource_id into product_id field.
Why do you need this feature?
Additional context
No response