You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I might well be missing something here, but I consider this a bug because it precludes leading/trailing spaces from ever being significant in input values. If the the caller of getInput wants to trim space on the value returned, they can make that decision. As things stand, leading/trailing spaces can never be significant in input values.
This puts input values at odds with environment variables on Linux and macOS (at least).
Please can someone provide the motivation behind this decision?
Thanks
To Reproduce
n/a
Expected behavior
Per above description.
Screenshots
n/a
Desktop (please complete the following information):
n/a
Smartphone (please complete the following information):
n/a
Additional context
None
The text was updated successfully, but these errors were encountered:
Describe the bug
As I raised over in the community forums, the core package trims the value returned by getInput:
toolkit/packages/core/src/core.ts
Line 74 in 432a78c
I might well be missing something here, but I consider this a bug because it precludes leading/trailing spaces from ever being significant in input values. If the the caller of
getInput
wants to trim space on the value returned, they can make that decision. As things stand, leading/trailing spaces can never be significant in input values.This puts input values at odds with environment variables on Linux and macOS (at least).
Please can someone provide the motivation behind this decision?
Thanks
To Reproduce
n/a
Expected behavior
Per above description.
Screenshots
n/a
Desktop (please complete the following information):
n/a
Smartphone (please complete the following information):
n/a
Additional context
None
The text was updated successfully, but these errors were encountered: