Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/devtools/projects/ng-devtools/src/lib/devtools-tabs/BUILD.bazel

69 lines
2.3 KiB
Text
Raw Normal View History

refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
load("//devtools/tools:ng_module.bzl", "ng_module")
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
load("@io_bazel_rules_sass//:defs.bzl", "sass_binary")
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
load("//devtools/tools:typescript.bzl", "ts_test_library")
load("//devtools/tools:defaults.bzl", "karma_web_test_suite")
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
package(default_visibility = ["//visibility:public"])
sass_binary(
refactor(devtools): make bazel labels follow snake case convention Previously, camel case was used for bazel labels in the devtools directory. This commit changes these labels to snake case except in the case where the label is identical to the directory name that the BUILD file is in.
2021-12-09 08:41:40 +00:00
name = "devtools_tabs_component_styles",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
src = "devtools-tabs.component.scss",
)
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
ng_module(
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
name = "devtools-tabs",
srcs = [
"devtools-tabs.component.ts",
],
angular_assets = [
"devtools-tabs.component.html",
refactor(devtools): make bazel labels follow snake case convention Previously, camel case was used for bazel labels in the devtools directory. This commit changes these labels to snake case except in the case where the label is identical to the directory name that the BUILD file is in.
2021-12-09 08:41:40 +00:00
":devtools_tabs_component_styles",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
],
deps = [
Revert "Revert "refactor(devtools): implement multiframe support in devtools page (#53934)" (#54629)" (#54805) This reverts commit 133319eba0008cb556f587bfc873c3eb55e1d2a5. PR Close #54805
2024-03-05 03:55:01 +00:00
"//devtools/projects/ng-devtools/src/lib:frame_manager",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"//devtools/projects/ng-devtools/src/lib:theme",
"//devtools/projects/ng-devtools/src/lib/application-environment",
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/directive-explorer",
feat(devtools): Implement initial DI debugging features in devtools (#51719) This commit introduces 2 new features into DevTools. Directive level dependency inspection: Users can now view which dependencies their directives have injected in the property viewer tab. This view displays not only the dependency but also the resolution path that was used to service the injection. Injector graph inspection: Users can now view a visualization of the element and environment hierarchies in their application. These trees are displayed separately but on the same page in the Injector Tree tab. User can click on individual injectors to view a list of all the providers configured in that injector, as well as highlight the resolution path from that injector to the root (with the corresponding environment injector connection highlighted as well). PR Close #51719
2023-10-05 08:00:31 +00:00
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/injector-tree:injector_tree",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/profiler",
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/router-tree",
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/tab-update",
"//devtools/projects/protocol",
"//packages/common",
"//packages/core",
"//packages/core/src/util",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
"@npm//@angular/material",
"@npm//@types",
refactor(devtools): run buildifier on bazel files
2021-11-21 23:19:47 +00:00
"@npm//rxjs",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
],
)
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
ts_test_library(
refactor(devtools): make bazel labels follow snake case convention Previously, camel case was used for bazel labels in the devtools directory. This commit changes these labels to snake case except in the case where the label is identical to the directory name that the BUILD file is in.
2021-12-09 08:41:40 +00:00
name = "devtools_tabs_test",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
srcs = ["devtools-tabs.spec.ts"],
deps = [
":devtools-tabs",
Revert "Revert "refactor(devtools): implement multiframe support in devtools page (#53934)" (#54629)" (#54805) This reverts commit 133319eba0008cb556f587bfc873c3eb55e1d2a5. PR Close #54805
2024-03-05 03:55:01 +00:00
"//devtools/projects/ng-devtools/src/lib:frame_manager",
refactor(devtools): enables typescript strict option (#53340) Enabling `strict` is part of an effort to improve the quality of the devtools code base. One of the direct side effect is to enable `noImplicitAny`, `strictPropertyInitialization` and `strictBindCallApply`. This commit also replaces `fullTemplateTypeCheck` with `stringTemplates`. PR Close #53340
2023-12-04 19:44:53 +00:00
"//devtools/projects/ng-devtools/src/lib:theme",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"//devtools/projects/ng-devtools/src/lib/application-environment",
refactor(devtools): enables typescript strict option (#53340) Enabling `strict` is part of an effort to improve the quality of the devtools code base. One of the direct side effect is to enable `noImplicitAny`, `strictPropertyInitialization` and `strictBindCallApply`. This commit also replaces `fullTemplateTypeCheck` with `stringTemplates`. PR Close #53340
2023-12-04 19:44:53 +00:00
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/directive-explorer",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"//devtools/projects/ng-devtools/src/lib/devtools-tabs/tab-update",
"//devtools/projects/protocol",
"//packages/common",
"//packages/core",
"//packages/core/src/util",
refactor(devtools): enables typescript strict option (#53340) Enabling `strict` is part of an effort to improve the quality of the devtools code base. One of the direct side effect is to enable `noImplicitAny`, `strictPropertyInitialization` and `strictBindCallApply`. This commit also replaces `fullTemplateTypeCheck` with `stringTemplates`. PR Close #53340
2023-12-04 19:44:53 +00:00
"//packages/core/testing",
"@npm//@angular/material",
"@npm//rxjs",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
],
)
karma_web_test_suite(
name = "test",
deps = [
refactor(devtools): make bazel labels follow snake case convention Previously, camel case was used for bazel labels in the devtools directory. This commit changes these labels to snake case except in the case where the label is identical to the directory name that the BUILD file is in.
2021-12-09 08:41:40 +00:00
":devtools_tabs_test",
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.
2021-12-16 07:00:43 +00:00
"//packages/common/http",
"//packages/platform-browser/animations",
build(devtools): migrate ng-devtools library to bazel Allows the ng-devtools library to be built with bazel. ng-devtools can now be used as a dependency in other bazel build rules.
2021-09-08 22:38:13 +00:00
],
)
Reference in a new issue Copy permalink