[Feedback] docs/components/pipelines/reference/component-spec.md

[donovat]

It would be great if you could also give an example of the use of the env within the implementation section of the component reference.
Plus in the example you use tags like -{name: Training data} and --train-set, {inputPath: Training data}. Yet later on in the page you reference --train-set, {inputPath: training_data} and training_data=some_task1.outputs['some_data'].
it's not clear if you should use training_data as this works when compiled, or Training data which does not work, and is not easy to see how to use in the pipeline section.

[uday-codes69]

Hi! @donovat I'd love to work on this issue as my first contribution to Kubeflow.
I’ll clarify the use of env and standardize the input name examples as suggested.
Could you please assign it to me? Thanks!

[donovat]

Hi @uday-codes69 - Does not look like I can assign the issue to yourself. I expect only the repo owners/managers can do that, so worth pinging one of those via the slack channel. - Sorry.

[uday-codes69]

ok @donovat

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.