Michael Fridman
Michael Fridman
Need to fix the parsing logic, which currently assumes all functions are named. But, they can also be inlined, for example: ```go func init() { goose.AddMigration(func(tx *sql.Tx) error { return...
Close #278 EDIT: I think I'd like to put this under `goose beta schema`, to denote that this is an unstable command and is experimental. And we can promote this...
### Proposal The default log output from this package is quite verbose. It would be ideal if the happy path (by default) logged as little as possible and reported only...
This issue will track all key tasks and issues needed to bring `tparse` to a stable `v1` release 🎉 . ## Bug fixes - [ ] #106 - [x] #126...
> go test -cover now prints coverage summaries for covered packages that do not have their own test files. Prior to Go 1.22 a go test -cover run for such...
Sometimes you want to see _just_ the failed test names. By default tparse prints package/test and the corresponding failure output, but these can add up. Not sure how to solve...
Picking up from https://github.com/mfridman/tparse/pull/95#issuecomment-1580742021, let's add color support to the package `-progress` output. Outside the scope of this PR, but as we flush out the functionality of `-progress`, we should...
Picking up from https://github.com/mfridman/tparse/issues/86#issuecomment-1564028742, @ti-mo has a nice suggestion to split tparse output and go test output when using `-follow`. Briefly, the `-follow` flag parses the `go test` json event...
Any chance we could get a new tag, maybe `v1.2.0`? There's been a few notable changes, https://github.com/mitchellh/protoc-gen-go-json/compare/2263edbfec9f3790d24c59cd38240f96a1fc2da2...49905733154f04e47d685de62c2cc2b72613b69e
This PR bumps the https://github.com/elastic/go-sysinfo dependency. This is to resolve an issue they fixed recently, https://github.com/elastic/go-sysinfo/pull/195 Whenever importing this vertica/vertica-sql-go driver, it produces a logged line due to its dependency...