NetSparkleUpdater / NetSparkleUpdater/NetSparkle
Support headers when downloading appcast
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 832
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
I just migrated fom Winsparkle because I needed fine grained control over download and it worked like a charm.
However I noticed a little feature which helped me to figure out users how many users didn't upgrade yet.
WinSparke used to set the user agent with the app name and version for the appcast get request.
Would you mind adding a property to set the headers to pass to the inner HttpClient so achieve the same feature?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file or test is named. Start by tracing the appcast download path and the inner HttpClient, then identify where request options are configured. Done means callers can configure headers for the appcast request and tests verify those headers are passed through.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100