You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 56ccb9d
Browse filesBrowse the repository at this point in the historyBrowse files
Handle live metadata and uppercase PEP 723 scripts (#1916)
## Summary
- Refresh the PEP 723 CodeLens from live text-document changes when an
inline block appears, disappears, or is edited.
- Avoid unnecessary CodeLens refreshes for edits confined to the script
body.
- Include every `.py` casing, including `.PY`, in bulk inline-script
setup discovery.
- Re-enable the Windows CodeLens integration suite after
#1911 was fixed.
## User scenarios fixed
- **S08:** Bulk setup now finds uppercase and mixed-case Python file
extensions.
- **S10:** Dirty inline metadata edits immediately request a CodeLens
recomputation instead of waiting for a save or later routing event.
- **S11:** Adding PEP 723 metadata to an unsaved ordinary Python file
immediately surfaces the setup CodeLens.
## Validation
- `npm run lint`
- `npm run compile-tests`
- `npm run unittest` — 2,830 passing, 7 pending
- `npm run smoke-test` — 30 passing, 1 pending
- `npm run e2e-test` — 4 passing
- `npm run integration-test` — all 9 live inline-script CodeLens tests
passed on Windows; the full suite had 58 passing, 8 pending, and one
unrelated environment-creation timeout
- Manual S08 verification confirmed `h03_UPPERCASE.PY` appears in the
bulk setup picker
- S10/S11 were verified in a real VS Code extension host through
CodeLens refresh events and provider output; visible UI automation was
avoided after focus restoration caused VS Code to cancel its debounced
rendered-lens refresh
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
0 commit comments