Codebase scan doesn't detect a .NET app's email provider
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp, typescript
Research direction
Start in src/services/warehouse-sources/detect.ts and read the existing manifest parsers and their tests. Add coverage for .csproj PackageReference entries and Directory.Packages.props, then check the server tool catalog for existing email provider signals to extend with NuGet package names. Done means a fixture test detects a provider referenced by a .NET project and the offer can receive that signal.
Written by the indexing model from the issue text.
Description
Problem
The Wizard's codebase scan can't tell which email provider a .NET app uses, so the transactional email offer in #1506 never shows for a .NET backend that sends email through a provider's package.
The scan in src/services/warehouse-sources/detect.ts reads package manifests for npm, PyPI, RubyGems, Cargo, CocoaPods, Composer, Go, Hex, Maven and Gradle, and pub. It has no parser for .NET projects, so a package a .csproj file references never becomes a signal. The tool catalog also has no NuGet package signals for email providers, so a parser alone would match nothing.
PostHog's .NET SDK sends transactional email too, so a .NET app is a backend the offer should reach.
What would fix it
- A
.csprojparser (andDirectory.Packages.propsfor central package management) that reads eachPackageReference'sIncludeinto anugetecosystem. - NuGet package names for the email providers the catalog already knows, in the server tool catalog.
- A test with a
.csprojfixture that references a provider's package, next to the existing manifest tests.
#1506 stays as it is. This is a follow-up.
- Dominant language
- TypeScript
- Stars
- 204
- Forks
- 54
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 51
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PostHog/wizard
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
PostHog/wizard#1460 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Self-driving setup: checkbox labels and Confirm button overlap wrapped description textMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PostHog/wizard#986 · 4 comments ·
Maintainers usually reply within 1 day
-
Intro shows "(detected)" after a manual pick from the detection-failed pickerPossibly taken @ShobhanKarthish claimed this 72 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
nip98: validateEvent skips the payload check for a string or bytes bodyMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nbd-wtf/nostr-tools#599 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LemmyNet/lemmy-ui#4442 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Zettlr/Zettlr#6664 · 1 comment ·
Maintainers usually reply within 1 day
-
Microsoft Outlook add attachment reads the binary field from item 0Possibly taken @joshbarros claimed this today. Openstatus:in-linear
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
n8n-io/n8n#44021 · 2 comments ·
Maintainers usually reply within 1 day