Expose Config object as optional input terminal
Issue #102
resolved
Would it be possible to expose the “Config File” object on the ConPane of “Read Config From File.vi”?
This would allow extension of the class.
Comments (3)
-
repo owner -
reporter An accessor for Filepath would be convenient, but I don’t see any dynamic dispatches being needed.
The use cases I’m contemplating include:
- Linting (validation of content based on schema)
- Adding/validating default fields such as checksum/version/scopes/tokens
- Extend to support hierarchical configuration and collections
I guess it would be nice to have a more abstract base class that can be extended to other sources as well (such as DBs or REST calls) for retrieving config.
-
repo owner - changed status to resolved
- Log in to comment
Easy to do. But what are you planning on extending to do? And would that require any dynamic dispatch terminals on other API functions?