reactiveui / reactiveui/ReactiveUI.SourceGenerators

[Bug]: Namespace ReactiveUI.SourceGenerators doesn't not exists in VS2022 when updated to 2.6.1

Open
#371 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
71
Forks
6
Avg merge
2d 1h
Merged PRs (30d)
4

Description

Describe the bug 🐞

A bug happened! (this sentence was in template, I better keep it, looks important and totally helpful)

After updating nuget to 2.6.1 from 2.5.1 I start seeing lots of errors eveyrwhere, when opening cs-files containing using ReactiveUI.SourceGenerators; or using [Reactive] attribute on partial properties:

The type or namespace name 'SourceGenerators' does not exist in the namespace 'ReactiveUI' (are you missing an assembly reference?)

The compilation runs without problems. It's only when editing files. Reverting back to 2.5.1 - no problems anymore.

Step to reproduce
  1. Update nuget ReactiveUI.SourceGenerators from 2.5.1 to 2.6.1
  2. Errors everywhere
Reproduction repository

No response

Expected behavior

This should happen... (oh yeah)

I expect updated version to just work, like previous. Seems not a case, no idea what went wrong exactly.

Screenshots 🖼️

No response

IDE

Visual Studio 2022

Operating system

Microsoft Windows 11 Pro

Version

10.0.26200 Build 26200

Device

PC

ReactiveUI Version

2.6.1

Additional information ℹ️

I will stick with 2.5.1 for now, it's not a problem.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the editor-only diagnostics in Visual Studio 2022 after updating ReactiveUI.SourceGenerators from 2.5.1 to 2.6.1, using a file with using ReactiveUI.SourceGenerators; and a partial property with [Reactive]. Compare both package versions to isolate the change; done means compilation and editing show no false missing-namespace or attribute errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
compilers, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.