You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
The current BUILD files contain only //closure/goog:base, closure_base_js_library() rules and alias()s for the others.
Some of the closure_base_js_library() rules require [edit: seem to expect] that the HTML incorporate some CSS from under //closure/goog/css, but that can't be done from Bazel due to closure/goog/css/BUILD being:
Any attempt to reference the CSS files (e.g. via a closure_css_library() rule) gets a message to the effect of:
ERROR: .../BUILD:7:20: no such target '@com_google_javascript_closure_library//closure/goog/css:autocomplete.css':
target 'autocomplete.css' not declared in package 'closure/goog/css' defined by
.../external/com_google_javascript_closure_library/closure/goog/css/BUILD; however, a source file of this name exists.
(Perhaps add 'exports_files(["autocomplete.css"])' to closure/goog/css/BUILD?) and referenced by '...:css'
At a minimum, it would be useful to include something like:
exports_files(glob(["*.css"]))
Even better would be to include actual relevant rules. (In this case closure_css_library() rules.)
The full list of BUILD files for which there seems to be no useful rules (and thus implies there is content that that is expected to be used, but that can't be) is:
closure/goog/css/BUILD
closure/goog/css/editor/BUILD
closure/goog/dom/testdata/BUILD
closure/goog/images/BUILD
closure/goog/images/tree/BUILD
closure/goog/labs/BUILD
The text was updated successfully, but these errors were encountered:
goog.ui isn't being maintained anymore. Maybe you can pull something working out of an older commit? But in general, your best bet would be to avoid using goog.ui at all.
Do the maintainer of any of those provide official 1st class support for the closure compiler under Bazel? A first pass search of each seems to suggest not. (That's the major check-box feature for me.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current BUILD files contain only
//closure/goog:base
,closure_base_js_library()
rules andalias()
s for the others.Some of the
closure_base_js_library()
rules require [edit: seem to expect] that the HTML incorporate some CSS from under//closure/goog/css
, but that can't be done from Bazel due toclosure/goog/css/BUILD
being:Any attempt to reference the CSS files (e.g. via a
closure_css_library()
rule) gets a message to the effect of:At a minimum, it would be useful to include something like:
Even better would be to include actual relevant rules. (In this case
closure_css_library()
rules.)The full list of
BUILD
files for which there seems to be no useful rules (and thus implies there is content that that is expected to be used, but that can't be) is:closure/goog/css/BUILD
closure/goog/css/editor/BUILD
closure/goog/dom/testdata/BUILD
closure/goog/images/BUILD
closure/goog/images/tree/BUILD
closure/goog/labs/BUILD
The text was updated successfully, but these errors were encountered: