Bump version to 0.5.0

Author: AJenbo

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "phpantom_lsp"
-version = "0.4.0"
+version = "0.5.0"
 edition = "2024"
 license = "MIT"
 

Cargo.toml

@@ -51,7 +51,6 @@ PHPantom focuses on deep type intelligence. Here's how it compares:
 - **Smart PHPDoc completion.** `@throws` detects uncaught exceptions in the method body, `@param` pre-fills from the signature, and tags are filtered to context and never suggested twice.
 - **Array shape inference.** Literal arrays offer key completion with no annotation. Nested shapes, spreads, and array functions like `array_map` preserve element types.
 - **Closure parameter inference.** `$users->map(fn($u) => $u->name)` infers `$u` as `User` from the collection's generic context.
-- **Generator body types.** `yield` and `$x = yield` resolve to the correct `TValue` and `TSend` from the generator's return annotation.
 - **Conditional return types.** PHPStan-style conditional `@return` types resolve to the concrete branch at each call site.
 - **Type aliases and shapes.** `@phpstan-type`, `@phpstan-import-type`, and `object{...}` shapes all resolve through to completions.
 - **Laravel Eloquent.** Relationships, scopes, accessors, casts, and Builder chains resolve end-to-end. No Larastan, no ide-helper, no database access required.

README.md

@@ -51,16 +51,17 @@ feature surface grows.
 | 20 | Workspace Symbols (`workspace/symbol`) | Low-Medium | LSP Features | [lsp-features.md §5](todo/lsp-features.md#5-workspace-symbols-workspacesymbol) |
 | 21 | Folding Ranges (`textDocument/foldingRange`) | Low | LSP Features | [lsp-features.md §12](todo/lsp-features.md#12-folding-ranges-textdocumentfoldingrange) |
 | 22 | Selection Ranges (`textDocument/selectionRange`) | Low | LSP Features | [lsp-features.md §13](todo/lsp-features.md#13-selection-ranges-textdocumentselectionrange) |
+| 100 | Formatting proxy (`textDocument/formatting`) | Medium | LSP Features | [lsp-features.md §19](todo/lsp-features.md#19-formatting-proxy-textdocumentformatting-textdocumentrangeformatting) |
 | 81 | Work-done progress for GTI and Find References | Low | LSP Features | [lsp-features.md §18](todo/lsp-features.md#18-work-done-progress-for-gti-and-find-references) |
 | 101 | Argument count diagnostic | Low | Diagnostics | [diagnostics.md §7](todo/diagnostics.md#7-argument-count-diagnostic) |
 | 88 | Early-exit and `Cow` return in `apply_substitution` | Low | Performance | [performance.md §7](todo/performance.md#7-recursive-string-substitution-in-apply_substitution) |
 | 87 | Reference-counted `ClassInfo` (`Arc<ClassInfo>`) | Medium | Performance | [performance.md §2](todo/performance.md#2-reference-counted-classinfo-arcclassinfo) |
 
 **After Sprint 3:** PHPantom feels like a complete LSP to everyday
-users. Outline, breadcrumbs, workspace search, folding, and smart
-select all work. Argument count errors catch real bugs and serve as
-a canary for type engine correctness. No one says "it's missing X"
-for basic editing workflows.
+users. Outline, breadcrumbs, workspace search, folding, formatting,
+and smart select all work. Argument count errors catch real bugs and
+serve as a canary for type engine correctness. No one says "it's
+missing X" for basic editing workflows.
 
 ---
 
@@ -95,26 +96,25 @@ actions.
 ## Sprint 5 — Polish for office adoption
 
 These items close the gaps that PHPStorm and VS Code + Intelephense
-users at the office would notice. PHPDoc generation and formatting
-are the most common "where did that go?" moments. Inlay hints are
-high-visibility in VS Code. The implementation error diagnostic
-reuses existing code action logic and pairs with the quick-fix.
-File rename on class rename removes a friction point that
-Intelephense premium users expect.
+users at the office would notice. PHPDoc generation is the most
+common "where did that go?" moment. Inlay hints are high-visibility
+in VS Code. The implementation error diagnostic reuses existing code
+action logic and pairs with the quick-fix. File rename on class
+rename removes a friction point that Intelephense premium users
+expect.
 
 | # | Item | Effort | Domain | Doc Link |
 |---|---|---|---|---|
 | 24 | PHPDoc block generation on `/**` | Medium | LSP Features | [lsp-features.md §3](todo/lsp-features.md#3-phpdoc-block-generation-on-) |
-| 100 | Formatting proxy (php-cs-fixer / phpcbf) | Medium | LSP Features | [lsp-features.md §19](todo/lsp-features.md#19-formatting-proxy-textdocumentformatting-textdocumentrangeformatting) |
 | 40 | Inlay hints (`textDocument/inlayHint`) | Medium | LSP Features | [lsp-features.md §9](todo/lsp-features.md#9-inlay-hints-textdocumentinlayhint) |
 | 102 | Implementation error diagnostic | Medium | Diagnostics | [diagnostics.md §9](todo/diagnostics.md#9-implementation-error-diagnostic) |
 | 99 | File rename on class rename | Medium | LSP Features | [lsp-features.md §20](todo/lsp-features.md#20-file-rename-on-class-rename) |
 | 103 | Stub extension selection (`[stubs] extensions`) | Low | Configuration | [config.md §stubs](todo/config.md#extension-stub-selection) |
 
 **After Sprint 5:** PHPantom is ready for office colleagues. They
-get formatting, PHPDoc generation, inlay hints, and the diagnostics
-they're used to. Nobody switching from Intelephense (free or
-premium) feels like they lost more than they gained.
+get PHPDoc generation, inlay hints, and the diagnostics they're used
+to. Nobody switching from Intelephense (free or premium) feels like
+they lost more than they gained.
 
 ---
 

docs/CHANGELOG.md

@@ -8,46 +8,14 @@ within the same impact tier.
 | **Impact** | **Critical**, **High**, **Medium-High**, **Medium**, **Low-Medium**, **Low** |
 | **Effort** | **Low** (≤ 1 day), **Medium** (2-5 days), **Medium-High** (1-2 weeks), **High** (2-4 weeks), **Very High** (> 1 month) |
 
-No quick fixes or refactoring suggestions exist today. No `codeActionProvider` in
-`ServerCapabilities`, no `textDocument/codeAction` handler, and no
-`WorkspaceEdit` generation infrastructure beyond trivial `TextEdit`s for
-use-statement insertion.
-
 **Refactoring code actions overview:** §3 (Extract Function), §7 (Inline
 Variable), §8 (Extract Variable), and §9 (Inline Function/Method) form
 the core refactoring toolkit. They share infrastructure for scope
 analysis, variable usage tracking, and `WorkspaceEdit` generation.
 
----
-
 ## 1. Implement missing abstract/interface methods
-**Impact: Medium · Effort: Medium**
-
-When a non-abstract class extends an abstract class or implements an
-interface but is missing required method implementations, offer a code
-action to generate stubs for all missing methods.
-
-### Behaviour
 
-- Detect the gap: resolve the full class hierarchy (already done by
-  `resolve_class_with_inheritance`), collect all abstract methods from
-  parent classes and all methods from implemented interfaces, subtract
-  the methods the class already defines.
-- Offer a code action: `Implement missing methods` (or list them
-  individually: `Implement Foo::bar`, `Implement Baz::qux`).
-- Generate method stubs at the end of the class body with:
-  - Correct visibility and static modifiers matching the interface/abstract declaration.
-  - Parameter names, type hints, and default values from the parent.
-  - Return type from the parent.
-  - PHPDoc block inherited from the parent (or `{@inheritDoc}`).
-  - Body: `throw new \RuntimeException('Not implemented');` or
-    `// TODO: Implement` — pick one convention.
-
-**Why this is a good first code action:** It exercises the full
-`codeActionProvider` → `WorkspaceEdit` → `TextEdit` pipeline without
-needing scope analysis or cross-file edits. The class hierarchy data
-is already fully resolved. This builds the infrastructure that Extract
-Function and other code actions depend on.
+No outstanding items. Shipped in the current release cycle.
 
 ---
 
@@ -157,7 +125,7 @@ variable X in this scope" as a natural byproduct.
 | Hover | "Resolve type at arbitrary position" — needed to type params |
 | Document Symbols (see `todo-lsp-features.md`) | AST range → symbol mapping — needed to find enclosing function and valid insertion points |
 | Find References (see `todo-lsp-features.md`) | Variable usage tracking across a scope — the same "which variables are used where" analysis |
-| Implement missing methods (§1) | Builds the code action + `WorkspaceEdit` plumbing |
+| Implement missing methods (§1, shipped) | Builds the code action + `WorkspaceEdit` plumbing |
 
 ---
 

docs/todo.md

@@ -1,6 +1,6 @@
 [package]
 name = "phpantom-zed"
-version = "0.4.0"
+version = "0.5.0"
 edition = "2021"
 publish = false
 license = "MIT"

docs/todo/actions.md

@@ -1,7 +1,7 @@
 id = "phpantom"
 name = "PHPantom"
 description = "PHP language support powered by PHPantom LSP, a fast and lightweight PHP language server."
-version = "0.4.0"
+version = "0.5.0"
 schema_version = 1
 authors = ["Anders Jenbo <anders@jenbo.dk>"]
 repository = "https://github.com/AJenbo/phpantom_lsp"