Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsitency in step development guidelines #886

Open
koral-- opened this issue Sep 11, 2023 · 0 comments
Open

Inconsitency in step development guidelines #886

koral-- opened this issue Sep 11, 2023 · 0 comments

Comments

@koral--
Copy link
Contributor

koral-- commented Sep 11, 2023

The guideline in this repo says:

Based on our experience the pipe character (|) works really well as a universal separator character, as it's quite rare in input values (compared to ,, ;, = or other more common separator characters).

https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md#input-naming-convention
And the same rule applies to the outputs.

However, the guideline on devcenter says:

expect the values to be provided as a newline character (\n) separated list (for example, first value\nsecond value).

https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/developing-a-new-step.html

It seems that all the steps use pipe as an output separator in fact so devcenter is incorrect?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant