We frequently have samples that host more than one listed asset in a single sample (e.g.: a mega-web-part sample, or a Power Fx sample).
To help increase exposure, we need to list each asset (e.g.: every web part, every Power Fx function) in the sample browser, even if they point to the same sample solution.
To do this, we'd most likely need to change the sample.json schema to handle an array of samples at the root, rather than a single sample.
We frequently have samples that host more than one listed asset in a single sample (e.g.: a mega-web-part sample, or a Power Fx sample).
To help increase exposure, we need to list each asset (e.g.: every web part, every Power Fx function) in the sample browser, even if they point to the same sample solution.
To do this, we'd most likely need to change the
sample.jsonschema to handle an array of samples at the root, rather than a single sample.