Iin octopus 2 there was a concept of layer features which listed features used in the layer that were not yet supported by octopus or rendering. We removed it however in octopus 2 public release as it was kinda broken.
This was used to find out how often a specific feature is used - the backend parser logged all such features in elasticsearch and we can see how often is every feature use to prioritize them.
Not sure if https://github.com/opendesigndev/octopus/issues/37 is a good candidate (might be too easy and obvious and we can just implement it right away) but in general it would be great to create similar concept of features - probably would fit into the manifest better than being on the layer level. Than we could run big collections in kraken could and calculate in what X% of designs is it used
Iin octopus 2 there was a concept of layer features which listed features used in the layer that were not yet supported by octopus or rendering. We removed it however in octopus 2 public release as it was kinda broken. This was used to find out how often a specific feature is used - the backend parser logged all such features in elasticsearch and we can see how often is every feature use to prioritize them. Not sure if https://github.com/opendesigndev/octopus/issues/37 is a good candidate (might be too easy and obvious and we can just implement it right away) but in general it would be great to create similar concept of features - probably would fit into the manifest better than being on the layer level. Than we could run big collections in kraken could and calculate in what X% of designs is it used