Files
sdk/pkg/front_end/pubspec.yaml
T
Paul Berry 599f4bf94e [messages] Move string extensions into analyzer_testing.
These extensions were previously in `pkg/analyzer_utilities`, which is
not published on `pub`. That meant they could not be used from within
the `lib` directory of any package that *is* published on
`pub`. Specifically, they could not be used from within
`pkg/analyzer_testing/lib`.

In a follow-up CL, I will modify the testing logic so that after
printing `To accept the current state, expect:`, it prints diagnostic
codes in their proper camelCase format.

Change-Id: I6a6a696432d7162906b2c235ea88310dc0aa1fa9
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/480040
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
2026-02-12 10:12:02 -08:00

44 lines
905 B
YAML

# Currently, front_end API is not stable and users should not
# depend on semver semantics when depending on this package.
name: front_end
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
environment:
sdk: ^3.9.0
workspace:
- testcases
resolution: workspace
# Use 'any' constraints here; we get our versions from the DEPS file.
dependencies:
_fe_analyzer_shared: any
kernel: any
package_config: any
yaml: any
# Use 'any' constraints here; we get our versions from the DEPS file.
dev_dependencies:
analyzer: any
analyzer_testing: any
analyzer_utilities: any
args: any
build_integration: any
compiler: any
dart_style: any
dart2wasm: any
dev_compiler: any
expect: any
json_rpc_2: any
path: any
pub_semver: any
test_reflective_loader: any
test: any
testing: any
vm_service: any
vm: any
web_socket_channel: any