Skip to content
New issue

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

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

Already on GitHub? # to your account

Fix coverage reporting #2477

Merged
merged 2 commits into from
Jan 3, 2023
Merged

Fix coverage reporting #2477

merged 2 commits into from
Jan 3, 2023

Conversation

gaborbernat
Copy link
Contributor

Signed-off-by: Bernát Gábor gaborjbernat@gmail.com

Signed-off-by: Bernát Gábor <gaborjbernat@gmail.com>
Signed-off-by: Bernát Gábor <gaborjbernat@gmail.com>
Copy link

@MeCorey MeCorey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

virtualenv activation module

Activate with overlay use activate.nu

Deactivate with deactivate, as usual

To customize the overlay name, you can call overlay use activate.nu as foo,

but then simply deactivate won't work because it is just an alias to hide

the "activate" overlay. You'd need to call overlay hide foo manually.

export-env {
def is-string [x] {
($x | describe) == 'string'
}

def has-env [name: string] {
    $name in (env).name
}

# Emulates a `test -z`, but btter as it handles e.g 'false'
def is-env-true [name: string] {
  if (has-env $name) {
    # Try to parse 'true', '0', '1', and fail if not convertible
    let parsed = do -i { $env | get $name | into bool }
    if ($parsed | describe) == 'bool' {
      $parsed

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

Successfully merging this pull request may close these issues.

2 participants