Skip to content
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

Add support for bazel build rules #141

Merged
merged 2 commits into from
Apr 12, 2018
Merged

Add support for bazel build rules #141

merged 2 commits into from
Apr 12, 2018

Conversation

paradoxengine
Copy link
Contributor

Adding a basic workspace and bazel rules.
The rules were generated via gazelle (blaze run :gazelle) and tuned a bit (e.g. changing visibility and adding the data dependency).
This should allow bazel users to just depend on the project without a local BUILD file.

Adding a basic workspace and bazel rules.
The rules were generated via gazelle (blaze run :gazelle) and tuned a bit (e.g. changing visibility and adding the data dependency).
This should allow bazel users to just depend on the project without a local BUILD file.
@codecov
Copy link

codecov bot commented Apr 11, 2018

Codecov Report

Merging #141 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #141   +/-   ##
=======================================
  Coverage   96.05%   96.05%           
=======================================
  Files           9        9           
  Lines        1065     1065           
=======================================
  Hits         1023     1023           
  Misses         23       23           
  Partials       19       19

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f881566...8ba446e. Read the comment docs.

Copy link
Member

@jeevatkm jeevatkm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@paradoxengine Could you please add details of build file on README.md?

Mention bazel support in the readme file.
Once this is committed, if useful, I can add a sample load statement and build config to depend on resty (I want to be sure it's tested first)
@paradoxengine
Copy link
Contributor Author

Sure, I've added some simple text, let me know if that's enough.
Bazel is a build system opensourced by Google: it manages dependencies differently than go and requires to have the WORKSPACE/BUILD files for folks to depend on it. The alternative is to essentially have the BUILD file on the caller side, which is not so great.

Copy link
Member

@jeevatkm jeevatkm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @paradoxengine

@jeevatkm jeevatkm merged commit db388cd into go-resty:master Apr 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants