find asset
This commit is contained in:
@@ -44,6 +44,23 @@
|
||||
- Repository and homepage links now point to the GitHub mirror; README links to both GitHub and Gitea.
|
||||
- Extension now activates in untrusted (Restricted Mode) workspaces; workspace-defined `ra3modxml.sdkPath` and `ra3modxml.additionalDataSearchPaths` are ignored until the workspace is trusted.
|
||||
|
||||
- **Find asset.** `RA3 Mod XML: Find asset (id or Type:Id)…` opens a search
|
||||
picker over the whole index: type `Type:Id`, an exact id or a partial id and
|
||||
the result list updates as you type (`Type:` alone lists every asset of that
|
||||
type). Rows show the asset type, origin (project / SDK / manifest), reference
|
||||
count and defining file; accepting one jumps to the definition. When a
|
||||
`type:id` is defined in several places (mod override + vanilla source +
|
||||
compiled manifest) a second picker chooses which definition to open. The
|
||||
query can also be prefilled from the current selection through the editor
|
||||
context menu entry.
|
||||
|
||||
### Fixed
|
||||
|
||||
- The editor context-menu entries were declared under a top-level `menus` key
|
||||
instead of `contributes.menus`, so VS Code never showed them. Adding the new
|
||||
search entry moved the block where it belongs; `Find unreferenced assets of
|
||||
this type` now appears in the editor context menu as documented.
|
||||
|
||||
## 0.1.24 — 2026-08-11
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user