Codebase scan doesn't detect a .NET app's email provider

Open
#1,527 1 comment 0 reactions 0 assignees View on GitHub

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
Domain
backend, tooling

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 .csproj parser (and Directory.Packages.props for central package management) that reads each PackageReference's Include into a nuget ecosystem.
  • NuGet package names for the email providers the catalog already knows, in the server tool catalog.
  • A test with a .csproj fixture 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

  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.

More from PostHog/wizard

All issues in PostHog/wizard

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.