commit | e2edbd8b176bb4337c9d71a5a18a79ab37b66721 | [log] [tgz] |
---|---|---|
author | Sanjay Chouksey <sanjayc@google.com> | Thu Jan 21 23:00:53 2021 +0000 |
committer | CQ Bot <commit-bot@chromium.org> | Thu Jan 21 23:00:53 2021 +0000 |
tree | b64bbf822d392e14e6e2f2fee18e87066c1a0204 | |
parent | 57733a1a5e72aec8e861ca68ab17dca26af4c0fa [diff] |
[ermine] Plumb url annotation from element proposal This change reads the url, id and name annotation from element proposal when a component is launched from external source (session_control). This helps identify the component given its url in e2e tests, since we can reliably add it to it's inspect data. Test: Updates clusters_model_test Change-Id: I0a2d395764be50481d4900c19d37b16dd9c8c5c4 Reviewed-on: https://fuchsia-review.googlesource.com/c/experiences/+/473867 Reviewed-by: Yeonhee Lee <yhlee@google.com> Commit-Queue: Sanjay Chouksey <sanjayc@google.com>
This is a companion repository to Fuchsia and contains code that either implements or supports user facing code for the Fuchsia platform. The code provides a majority of the user interface for the Workstation product as well as a small set of examples, tests, and benchmarks.
This repository is a “source petal” included in the Fuchsia Platform Source Tree (FPST) checkout. Code in this repository must be built with Fuchsia in order to be functional, see (the guide)[https://fuchsia.dev/fuchsia-src/development/source_code] for instructions on getting the source.
Hardware support should be considered experimental. However, NUC's and Pixelbooks are known to work best. For details on hardware setup see: (Install Fuchsia on a Device)[https://fuchsia.dev/fuchsia-src/development/hardware/paving]
Once you have functional checkout you can (configure a build)[https://fuchsia.dev/fuchsia-src/development/build/fx#configure-a-build] targeting Workstation:
fx set workstation.<board> # For options run: `fx list-boards` fx build
See Fuchsia's (build and pave instructions)[https://fuchsia.dev/fuchsia-src/development/build/build_and_pave_quickstart] for detailed instructions.
Once built, standard Fuchsia workflows for paving, running code, and testing apply. See: (fx workflows)[https://fuchsia.dev/fuchsia-src/development/build/fx] for detailed instructions.