-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add bazel tests #1
chore: add bazel tests #1
Conversation
Is the error happening in the test module? If so it just looks like you're missing a |
Oh duh that was it. What do I do about there being no real test files with this module? There is |
Nevermind I read the jamfile more closely and know how to test it! |
Okay so here is the issue I need help solving. The way to test is to do a |
…e tries to include
Is there a reason |
Oh yeah... Did that and it got me new errors so I will forge ahead. Thank you! |
@zaucy Can you add the CI workflow? Or is there a way I can add it? |
Its the yaml file in the |
Sounds good! Thank you for the pointer |
CI added! |
All the tests pass now! |
Let me know when you update the registry so I can move onto serialization. |
its released! |
Thank you! |
This is just the initial commit to let @zaucy know that I am working on this module next. I am wondering on your thoughts on this error. I know what it is trying to say but afaik I am including the dependency right in the
MODULE.bazel
file and thetest/MODULE.bazel
file references the former correctly.Also this happens with every dependency. The top level builds just fine.