Give the example/ directory its own workspace file #13
Conversation
This makes it more obvious how to bootstrap a new project with `rules_gqlgen`. Also, clean up the README.md a bit and remove references to "GoLang". Fixes #11
bcspragu
force-pushed
the
brandon/example-workspace
branch
from
62311ba to
ebf241b
Compare
|
What do you use for your editor? I am using Intellij and loading the rules_gqlgen project shows the example dir as excluded from the project. I posted in the Bazel slack asking what others do in this situation where there are multiple WORKSPACE, but haven't gotten any response so far. I may post on the Bazel google group about it. If I remove example from .bazelignore, it breaks the build for me, so that's not an option either. |
I'm using Helix, which is basically just a text editor when it comes to Bazel stuff. I think the correct behavior would be to treat any sub-WORKSPACE as it's own project, with a second-best choice being to ignore anything in a sub-WORKSPACE, but I'm wholly ignorant of IntelliJ, so I don't know what the expected/best-case behavior would be |
This makes it more obvious how to bootstrap a new project with
rules_gqlgen.Also, clean up the README.md a bit and remove references to "GoLang".
Fixes #11