| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
interfaces.
RELNOTES: None.
PiperOrigin-RevId: 201735466
|
| |
|
|
|
|
|
| |
mandatoryPositionals is going away soon. While it is less verbose than the alternative, it does not allow for documentation to be specified (nor type-checking), and is thus inferior to the alternative. Killing mandatoryPositionals will also make the interpreter code cleaner.
RELNOTES: None.
PiperOrigin-RevId: 201566377
|
| |
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 200260766
|
| |
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 200096226
|
| |
|
|
|
|
|
|
| |
I don't know much about most of this code, but there should be no functional
changes.
RELNOTES: none
PiperOrigin-RevId: 198773657
|
| |
|
|
|
|
|
|
| |
Fortunately or unfortunately, Skylark doesn't seem to validate against this
type, so tests don't pick this mistyping up.
RELNOTES: none
PiperOrigin-RevId: 198568282
|
| |
|
|
|
|
|
|
|
|
| |
I didn't catch it at the time this field was initially introduced, but R files
from Android libraries, exposed via AndroidResourcesInfo, are compiletime only.
They should not be used at runtime or inherited from dependencies. Rename the
field and add this warning to the description.
RELNOTES: none
PiperOrigin-RevId: 198448391
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Expose the Android data processing API to skylarkbuildapi
Rather than pass the SkylarkBuildApi interfaces (e.g., FileApi instead of
Artifact) all the way through the Android data processing code, instead just
cast them to the correct Bazel types. This is ugly, but is probably better than
having to do multiple refactorings of the Android code. (A similar refactoring,
for just a single type, took about 10 changes and 3300 lines of code.) The
Skylark Build API is only meant for things exposed to Skylark, not Bazel
internals, and, besides, when building with Bazel we should only expect inputs
from other parts of Bazel.
RELNOTES: none
PiperOrigin-RevId: 198438519
|
|
|
Expose all Android data info classes as interfaces in skylarkbuildapi. Most
methods are not exposed in the interface since they are not exposed in Skylark.
In fact, stop exposing a few methods from AndroidResourcesInfo that are exposed
but shouldn't be.
RELNOTES: none
PiperOrigin-RevId: 198396677
|
cparsons
asteinb