John Lenton
John Lenton
The output produced by `WriteHelp` and `WriteManPage` is inconsistent, and in particular `WriteHelp` seems wrong, when a command provides `Usage()`. Given ```go package main import ( "fmt" "os" "github.com/jessevdk/go-flags" )...
Without this change, groups that are commands but that don't satisfy (*Group).showInHelp() would be skipped when working out the alignment, which would result in negative lengths when trying to process...
I'm afraid I introduced a bug in fixing #278: now this ```go package main import "github.com/jessevdk/go-flags" import "os" type options struct { Positional struct { Bar string `description:"bar"` } `positional-args:"yes"`...
We'd like to make charm authors lives easier by implementing the following idea, from @stub42: ```python def __init__(self, *args, **kwargs): # [...] deps = Dependencies( PostgreSQLDependency(dbname='mydb', extensions=['citext']), StorageDependency('backups'), ValidCharmConfig(self.charm), )...
I'd rather know early if there are snapshots that need cleaning up, rather than finding out while adding something unrelated. Keeps things tidy. I thought of giving Cleanup() this behaviour...
fixes #55.
I believe this is from 1.15 on (read a [long discussion] if you're interested): ``` $ go test ./... # github.com/beme/abide ./abide_test.go:25:9: conversion from int to string yields a string...
This allows writing something like systems: [ubuntu-*, -ubuntu-14*] which is much shorter and future-proof than what's allowed with the stricter never-mix-plain-and-delta rule. Also, adds a unit test for evalstr.
If I have an environment value that has double quotes, ```yaml environment: foo: 'some "quoted value"' ``` then spread will (incorrectly) do ```sh export foo="some "quoted value"" ``` which sets...
It would be handy to have a SKIP command you could use from prepare to skip a test or variant when conditions for it aren't met. Right now I'm having...