Google Git
Sign in
dart / sdk / d35c01e8c6406ee10d75485ceba489037ba0d18c
commitd35c01e8c6406ee10d75485ceba489037ba0d18c[log] [tgz]
authorDanny Tuppeny <danny@tuppeny.com>Wed May 07 07:56:18 2025 -0700
committerCommit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 07 07:56:18 2025 -0700
tree1d35c8dfe43e350519108389bb6d136d8fa59eb0
parentee16e3625edd62250a45c19f6d0ac27d23c6c0cc [diff]
[analysis_server] Extract computing CodeActions from the textDocument/codeAction handler

In an upcoming change, we will need to be able to compute code actions from a command handler (to handle applying a code action as a result of a command call).

This change just extracts the main computation of code actions out of the handler into a new class that can be reused there.

This change is largely just a cut/paste, but I did extract a number of inline functions to be class-level (the variables they required are now at the class level) to reduce some nesting.

Change-Id: I438cfc07edfef9fa6d98c8e29c183b30abcf82d4
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/427220
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Samuel Rawlins <srawlins@google.com>
2 files changed
tree: 1d35c8dfe43e350519108389bb6d136d8fa59eb0
  1. .dart_tool/
  2. .github/
  3. benchmarks/
  4. build/
  5. docs/
  6. pkg/
  7. runtime/
  8. samples/
  9. sdk/
  10. tests/
  11. third_party/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitattributes
  16. .gitconfig
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .style.yapf
  21. AUTHORS
  22. BUILD.gn
  23. CHANGELOG.md
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. PATENT_GRANT
  30. PRESUBMIT.py
  31. pubspec.yaml
  32. README.dart-sdk
  33. README.md
  34. sdk.code-workspace
  35. sdk_args.gni
  36. sdk_packages.yaml
  37. SECURITY.md
  38. WATCHLISTS
README.md

Dart

An approachable, portable, and productive language for high-quality apps on any platform

Dart is:

  • Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.

  • Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.

  • Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.

Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:

  • Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.

  • Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).

Dart platforms illustration

License & patents

Dart is free and open source.

See LICENSE and PATENT_GRANT.

Using Dart

Visit dart.dev to learn more about the language, tools, and to find codelabs.

Browse pub.dev for more packages and libraries contributed by the community and the Dart team.

Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).

Building Dart

If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.

There are more documents in our repo at docs.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

Roadmap

Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.