Extend feature set and/or feature metadata
See original GitHub issueThis issue tracks the addition of new fields to the current feature set specification that allow a user to add metadata to either the feature set or features. These fields are optional and are intended to provide users with the flexibility to include feature level or feature level information.
The current proposal is to only add a single string field called description
to FeatureSpec
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Software Guide Software Development Kit V3.15
Boolean features can only be set to one of two possible values, representing the ... andor.com. SDK 3. METADATA. 4.4. Metadata can be...
Read more >Andor iQ3 USER GUIDE - BioDIP
The products can be configured with Andor and third party products and provide market leading performance and functionality. Please contact us for more....
Read more >Release Notes - FUSION Software Guide
Extend and customize the capabilities of your system in an open framework. Remotely control Fusion to execute protocols, set device features and more....
Read more >Welcome to AndorSDK2's documentation! - PythonHosted.org
The Andor instance is just a container for other objects that control various aspect of the camera: Info : camera information and available...
Read more >Andor & Better Call Saul Are Two of the Year's Best Shows
Andor has already set a date to start shooting its second (and final) season, making a premature ... This is a feature, not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Unless there are any objections, we will implement
labels
as amap<string, string>
at the feature level for 0.5. We will also add basic getters/setters at the feature set level. We will leave the discovery implementation for future releases.Please vote with a thumbs down if you want to discuss this further.
Completely agree that feature level makes sense. As an end user, that is likely how I would expect to use it.
From my point of view, I don’t think we are at a point of a more concrete set of requirements, so happy to leave that for a later point.