Skip to content

Conversation

@jcouv
Copy link
Member

@jcouv jcouv commented Mar 25, 2025

No notable conflicts

genlu and others added 30 commits February 26, 2025 16:25
This diagnostic is always hidden (no UI) for the sole support of the
associated code fix provider.
…eatures' into dev/maryamariyan/fixer-simplified

 Conflicts:
	src/Features/CSharp/Portable/Copilot/CSharpCopilotNotImplementedMethodFixProvider.cs
to keep the throw statement/expression check

- Adds more test
- Removes dead code
- [ ] Cleanup more code
- [ ] Fix failing tests
- [ ] Rename API make consistent
- [ ] Revisist triple slash docs
- [ ] Change SyntaxNode to MemberDeclaration
- [ ] Remove unexpected null checks
    - [x] Adds more test
    - [x] Removes dead code
    - [x] Cleans up more code
    - [ ] Fix failing tests
    - [x] Renames API to make consistent
    - [x] Revisits triple slash docs
    - [x] API Accepts SyntaxNode
    - [x] Removes unreachable code
- and do minor Cleanup
- [ ] Fixer seems not activates in tests
- Test correction on placement of diagnostic span
CyrusNajmabadi and others added 14 commits March 25, 2025 10:26
We've nullable disabled a bunch of files in the IDE, for reasons i don't
understand. Our code should be nullable safe. And if not, we should fix
it. I'm enabling nullability on roslyn ide.
* add remarks to documentation if available

* add named parameter for nulls
* Create new folder structure for Razor EA.

/Shared : will eventually be the area for all source items shared between
the current EA and the new EA.Razor.Features
/Features : will have an EA that is restricted to depending only on the
features layer. This will help provide a way to ship a more sane EA
structure for VS Code as well as reduce the likelyhood and work required
for a dual insertion
/EditorFeatures : contains the current EA. The project name is kept the
same for now but the folder is moved. This denotes that the binary does
depend on the EditorFeatures layer in Roslyn
@jcouv jcouv self-assigned this Mar 25, 2025
@ghost ghost added the untriaged Issues and PRs which have not yet been triaged by a lead label Mar 26, 2025
@dotnet-policy-service dotnet-policy-service bot added VSCode Needs API Review Needs to be reviewed by the API review council labels Mar 26, 2025
@dotnet-policy-service
Copy link
Contributor

This PR modifies public API files. Please follow the instructions at https://github.com/dotnet/roslyn/blob/main/docs/contributing/API%20Review%20Process.md for ensuring all public APIs are reviewed before merging.

@jcouv jcouv marked this pull request as ready for review March 26, 2025 02:56
@jcouv jcouv requested review from a team as code owners March 26, 2025 02:56
@jcouv jcouv requested a review from AlekseyTs March 26, 2025 03:06
@jcouv jcouv merged commit 2829b23 into dotnet:features/extensions Mar 26, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Compilers Needs API Review Needs to be reviewed by the API review council untriaged Issues and PRs which have not yet been triaged by a lead VSCode

Projects

None yet

Development

Successfully merging this pull request may close these issues.