Skip to content
This repository has been archived by the owner on May 31, 2024. It is now read-only.

Add Documentation - How to expose input in config file? #313

Open
dgarijo opened this issue Nov 5, 2020 · 2 comments
Open

Add Documentation - How to expose input in config file? #313

dgarijo opened this issue Nov 5, 2020 · 2 comments
Assignees
Labels

Comments

@dgarijo
Copy link
Contributor

dgarijo commented Nov 5, 2020

We don't specify how to do this. We do it for parameters, but inputs can also be declared in config files. Therefore we should follow a similar approach in case this happens. Otherwise mic will look for exactly the same file, and it will fail

@dgarijo dgarijo added enhancement New feature or request question labels Nov 5, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.71. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@dgarijo
Copy link
Contributor Author

dgarijo commented Nov 5, 2020

This can be done the same way parameters are done. But it's not documented!!

TO DO: Add in the documentation that this is possible

@dgarijo dgarijo self-assigned this Nov 5, 2020
@dgarijo dgarijo changed the title How to expose input in cofig file? How to expose input in config file? Jan 22, 2021
@mosoriob mosoriob changed the title How to expose input in config file? Add Documentation - How to expose input in config file? Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant