"Invalid type for dependent function" does not have any context #240
Labels
Comments
natefinch
pushed a commit
that referenced
this issue
Jul 18, 2019
mojzesh
pushed a commit
to mojzesh/mage
that referenced
this issue
Oct 12, 2019
magefile#241) This change adds a location of mg.Deps invocation, shrinking the search space from "all your build scripts" to "this particular mg.Deps invocation"
mojzesh
pushed a commit
to mojzesh/mage
that referenced
this issue
Oct 12, 2019
magefile#241) This change adds a location of mg.Deps invocation, shrinking the search space from "all your build scripts" to "this particular mg.Deps invocation"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an invalid kind of dependency is passed into
mg.Deps, then it's pretty hard to nail down what has happened, as the error message does not provide any location where that happened:Error: Invalid type for dependent function: func(string, string). Dependencies must be func(), func() error, func(context.Context), func(context.Context) error, or the same method on an mg.Namespace.It would be nice to be able to point to at least
mg.Depsinvocation, or, better, to the argument that caused the problem.The text was updated successfully, but these errors were encountered: