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
During testing, we need test against various versions of Bash (#18).
Some of Sheldons functions will work on older versions of Bash.
For the tests, we should be able to specify which function can be tested against a particular Bash version so that we can even test on older versions of Bash to show users what functions can be used in which version of Bash.
I'm thinking of something along the lines of a comment at the top of a function like:
.
.
.
## @returns Strings in $2 with the glue string, $1.
## @compatibility 3.2+
################################################################################
Sheldon.Util.String.join() {
local trim
.
.
.
When running tests:
Docker container, which runs the test, should have an env var indicating Bash version
Parse file and match pattern: ^Sheldon.<camel cap dir name>.<camel cap basename>.+\(\)\s\{$
Read lines above until @compatibility [0-9](\.[0-9]{2}[\+<>=]{2})$ is found
If matched version is equal to or greater than Docker's Bash version, run the test. Else skip while notifying user of incompatibility.
The text was updated successfully, but these errors were encountered:
During testing, we need test against various versions of Bash (#18).
Some of Sheldons functions will work on older versions of Bash.
For the tests, we should be able to specify which function can be tested against a particular Bash version so that we can even test on older versions of Bash to show users what functions can be used in which version of Bash.
I'm thinking of something along the lines of a comment at the top of a function like:
When running tests:
^Sheldon.<camel cap dir name>.<camel cap basename>.+\(\)\s\{$
@compatibility [0-9](\.[0-9]{2}[\+<>=]{2})$
is foundThe text was updated successfully, but these errors were encountered: