| commit | 7838e91a61d4bedab52cc2c4539d9f3273507e98 | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Tue Dec 04 01:35:22 2018 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Dec 04 01:35:22 2018 |
| tree | 462bb3e2ca7a6ee3f0db31c631bf58795bff1f4e | |
| parent | be44241dffad53ad0fb0bb38a726138f5ab66f98 [diff] |
[lucicfg] Implement 'graph.key(typ1, id1, typ2, id2, ...)' internal API. Config entities will be defined as named nodes in a DAG. graph.key(...) returns an opaque label that identifies such a node. We intern keys to make their identities (~address) match their values 1-to-1. That allows them to be used as keys in Starlark dicts and Go maps right away, without any additional code. R=nodir@chromium.org BUG=833946 Change-Id: I4db550081e331b2e4c49761ac581f0543814e213 Reviewed-on: https://chromium-review.googlesource.com/c/1357257 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.