Skip to content
Permalink
Browse files

Fix Bazel build breakage introduced in []

This is no way to make Blaze and Bazel happy at the same point. Without [] Blaze complains about import orders. However the new order breaks Bazel. Bazel suggested to add a suppression to suppress order check, which fixes the Bazel problem, but the suppression string is not recognized by Blaze.

I cannot think of another way to solve this other than MOE. Luckily we'll delete all the BUILD files when we move to Gradle anyway.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=237501133
  • Loading branch information...
jianglai committed Mar 8, 2019
1 parent f681ec2 commit 251a25589082cad1388c0f67d81d7e1cbd46e410
Showing with 2 additions and 0 deletions.
  1. +1 −0 java/google/registry/ui/js/BUILD
  2. +1 −0 java/google/registry/ui/js/registrar/BUILD
@@ -14,6 +14,7 @@ closure_js_library(
"JSC_IMPLICITLY_NULLABLE_JSDOC",
"JSC_DEPRECATED_PROP_REASON",
"JSC_STRICT_INEXISTENT_PROPERTY",
"JSC_REQUIRES_NOT_SORTED",
],
deps = [
"//java/google/registry/ui/soy",
@@ -14,6 +14,7 @@ closure_js_library(
"JSC_IMPLICITLY_NULLABLE_JSDOC",
"JSC_DEPRECATED_PROP_REASON",
"JSC_STRICT_INEXISTENT_PROPERTY",
"JSC_REQUIRES_NOT_SORTED",
],
deps = [
"//java/google/registry/ui/js",

0 comments on commit 251a255

Please sign in to comment.
You can’t perform that action at this time.