cszczepaniak
cszczepaniak
## Summary `assert.Eventually` waits for the tick interval before doing the first check of the condition. In a lot of cases, the condition might be true immediately, so it would...
## Description Addresses #424. Displays key in both the flag list and the deleted flag list. This makes it easier/more convenient to use the key as the name of the...
Flag keys can be changed from the generated key to have a descriptive name. It would be nice to show the key in the UI. ## Expected Behavior Flag key...
I use this as part of a pre-commit git hook and also sometimes in large batches of files, so it would be nice to have the option of passing in...
You can write keyword blocks with or without parentheses: ``` if (true) end ``` vs. ``` if true end ``` A nice feature would be to control whether or not...
This is a nice tool. I wonder what you'd think about extending it to include more git features? The top one I can think of right now would be git-smart-delete:...
## Summary Addresses #1424. `Eventually` and `EventuallyWithT` current must always wait at least the polling duration before they can succeed. This PR starts checking the condition immediately. The assertion still...
`assert.Eventually` does not check initially whether the condition is satisfied. This means it must [wait a minimum of the tick duration](https://github.com/stretchr/testify/blob/master/assert/assertions.go#L1850) before checking the condition for the first time. It...
Currently, `Eventually` and `EventuallyWithT` spin up a goroutine per condition check. It also sets the ticker channel to `nil` while the condition is being checked, which makes it hard to...
My setup: - wezterm in WSL2 - tmux 3.0a - neovim 0.10.0 When I call `:call VimuxRunCommand("echo 'foobar'")`, I get `o 'foobar'` printed where my cursor was in the buffer....