Google Git
Sign in
chromium / infra / luci / luci-go / fd05f62098d8b16e712695bf2b97b7a4d52d2d90
commitfd05f62098d8b16e712695bf2b97b7a4d52d2d90[log] [tgz]
authorPietro Scuttari <pietroscutta@google.com>Tue Apr 01 09:45:35 2025
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 01 09:45:35 2025
treecdcd5764a2dca65cd6ca7bb7bdffc15af1199804
parent42d415f524bfb8c68d9bac6a8cf0515c37c5d90e [diff]
[fleet-console-ui] Save visible columns in local storage

If the user comes back to the fleet console they should view the same columns they left behind.
At the same time if they get sent a link that specifies specific columns that should take precedence.

I also made it so local storage only gets updated when the column visibility changes, this means that if you get a link with some visible columns specified and don't modify them the next time you load the fleet console you will go back to your previous saved view.

Demo: https://18018-f13e83e-pietro-save-colums-in-localstor-dot-luci-milo-dev.appspot.com/ui/fleet/labs/devices

Change-Id: I35a0ec01433ba6d947d818b88566465d4b36f5b4
Bug: b/406958315
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/6405543
Reviewed-by: Piotr Grabski-Gradziński <piotrgg@google.com>
Commit-Queue: Piotr Grabski-Gradziński <piotrgg@google.com>
Auto-Submit: Pietro Scuttari <pietroscutta@google.com>
9 files changed
tree: cdcd5764a2dca65cd6ca7bb7bdffc15af1199804
  1. analysis/
  2. appengine/
  3. auth/
  4. auth_service/
  5. bisection/
  6. build/
  7. buildbucket/
  8. casviewer/
  9. cipd/
  10. cipkg/
  11. client/
  12. common/
  13. config/
  14. config_service/
  15. cv/
  16. deploy/
  17. examples/
  18. gae/
  19. gce/
  20. grpc/
  21. hardcoded/
  22. led/
  23. logdog/
  24. luci_notify/
  25. lucicfg/
  26. lucictx/
  27. luciexe/
  28. mailer/
  29. milo/
  30. mmutex/
  31. provenance/
  32. recipes_py/
  33. resultdb/
  34. scheduler/
  35. scripts/
  36. server/
  37. source_index/
  38. standalone/
  39. starlark/
  40. swarming/
  41. teams/
  42. third_party/
  43. tokenserver/
  44. tools/
  45. tree_status/
  46. vpython/
  47. web/
  48. .gitallowed
  49. .gitignore
  50. .go-lintable
  51. AUTHORS
  52. codereview.settings
  53. CONTRIBUTING.md
  54. CONTRIBUTORS
  55. go.mod
  56. go.sum
  57. LICENSE
  58. OWNERS
  59. PRESUBMIT.py
  60. README.md
  61. staticcheck.conf
  62. tools.go
  63. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoReference

Installing

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

It is now possible to directly install tools with go install:

go install go.chromium.org/luci/auth/client/cmd/...@latest
go install go.chromium.org/luci/buildbucket/cmd/...@latest
go install go.chromium.org/luci/cipd/client/cmd/...@latest
go install go.chromium.org/luci/client/cmd/...@latest
go install go.chromium.org/luci/cv/cmd/...@latest
go install go.chromium.org/luci/gce/cmd/...@latest
go install go.chromium.org/luci/grpc/cmd/...@latest
go install go.chromium.org/luci/logdog/client/cmd/...@latest
go install go.chromium.org/luci/luci_notify/cmd/...@latest
go install go.chromium.org/luci/lucicfg/cmd/...@latest
go install go.chromium.org/luci/luciexe/legacy/cmd/...@latest
go install go.chromium.org/luci/mailer/cmd/...@latest
go install go.chromium.org/luci/mmutex/cmd/...@latest
go install go.chromium.org/luci/resultdb/cmd/...@latest
go install go.chromium.org/luci/server/cmd/...@latest
go install go.chromium.org/luci/swarming/cmd/...@latest
go install go.chromium.org/luci/tokenserver/cmd/...@latest
go install go.chromium.org/luci/tools/cmd/...@latest

Contributing

Contributing uses the same flow as Chromium contributions.