Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Replace js provider methods with named parameters. | Pedro Liberal Fernandez | 2016-08-29 |
| | | | | | -- MOS_MIGRATED_REVID=131576962 | ||
* | Display all allowed types for SkylarkSignature Params that allow multiple | David Chen | 2016-07-05 |
| | | | | | | | | | | | | | | | | | | | types. Fixes #921 Certain parameters, such as the `executable` and `command` parameters of ctx.action, allow multiple types. However, the allowed types are not enumerated in the SkylarkSignature annotation, causing the generated Skylark Library document to not display any type information for those params. This change adds a new field, `allowedTypes`, to `SkylarkSignature` that is a list of `ParamType` objects. If the param can accept multiple types, then `type` is set to `Object.class`, and `allowedTypes` is set to the list of types that can be accepted. -- MOS_MIGRATED_REVID=126617047 | ||
* | Use only one list of parameters for SkylarkSignature | Damien Martin-Guillerez | 2016-06-14 |
| | | | | | | | | | | | | | Optional and named parameters are now specified using `defaultValue` and `named` (and `positional`). The new structure allow for parameters that are both named and positional (which was forbidden before). This new structure will be used to give the @SkylarkCallable annotation the possibility to provide named and default arguments. It should be a functional no-op for Bazel users. -- MOS_MIGRATED_REVID=124821455 | ||
* | Extract the @Param annotation from @SkylarkSignature | Damien Martin-Guillerez | 2016-06-10 |
The @SkylarkCallable annotation is very limited and to extend it it is best to share a similar API than the @SkylarkSignature annotation. -- MOS_MIGRATED_REVID=124473056 |