Skip to content

Tools.go causes package conflict #162

Description

@andyleap

When trying to vendor this package into a bazel environment, tools.go package name "tools" is conflicting with the rest of the go files. This is due to the fact that gazelle generation largely ignores build tags in it's initial phase. Is there any way that file could either get the package matched or moved into it's own directory? Happy to make a PR for that either way...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions