mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-07 20:39:31 +08:00
This reverts commitc2ad98d783. Reason for revert: fixed flakey test Original change's description: > Revert "Add header context menu to data grid" > > This reverts commit6bdb3622bd. > > Reason for revert: Interaction tests started failing on mac. > > https://ci.chromium.org/ui/p/devtools-frontend/builders/ci/Stand-alone%20Mac/2514/overview > > Original change's description: > > Add header context menu to data grid > > > > This CL adds a default header context menu to the data grid that lists visible > > and sortable columns much like the legacy data grid. > > > > Bug: 1150793 > > Change-Id: I84a8a9cc511d6be9fee1f89ba41a6e8649df54ec > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2600723 > > Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> > > Reviewed-by: Paul Lewis <aerotwist@chromium.org> > > TBR=aerotwist@chromium.org,jacktfranklin@chromium.org > > Change-Id: Ic8ef16044716d922d3a37b6a8fb32e13a75dee72 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 1150793 > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2601962 > Reviewed-by: Jan Scheffler <janscheffler@chromium.org> > Commit-Queue: Jan Scheffler <janscheffler@chromium.org> TBR=aerotwist@chromium.org,szuend@chromium.org,janscheffler@chromium.org,jacktfranklin@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1150793 Change-Id: Ibd352be261d2cefee6fccc4b18b438faaad57631 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2610596 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Paul Lewis <aerotwist@chromium.org> Reviewed-by: Jan Scheffler <janscheffler@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Components dev server
This server serves up examples of the web components built within DevTools and provides a useful way to document various states of components.
For more background, see the initial proposal and design doc.
To add an example for your component:
- Create
front_end/component_docs/DIRwhereDIRis the name of your component. - Within the new
DIR, add HTML files. Each one of these is a standalone example. You should name the HTML file based on what it's documenting, e.g.basic.htmlordata-missing.html. This file should import your component and render it with the data you need. - Create a
BUILD.gnin your newDIR. This should contain the following code:
import("../../../scripts/build/ninja/copy.gni")
copy_to_gen("elements_breadcrumbs") {
sources = [
"example1.html",
# list all other examples here
]
deps = [
# Any dependencies your examples rely on.
# For example, if they depend on code in the elements module:
"../../elements"
]
}
- Update
front_end/component_docs/BUILD.gnto add your new directory'sBUILD.GNto thepublic_depsarray. - Run
npm run components-serverto fire up a server onlocalhost:8090. You should now see your component listed and you can click on the link to view the examples. - Note: the server assumes your built target is
Default. If not, run the server and pass the--targetflag:npm run components-server -- --target=Release.