Update docs to not use resolutionPath?

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
fsharp, sql

Research direction

Review the documentation samples that use resolutionPath and compare them with the now-specific NuGet packages for each database type. Update the generic examples to use the specific packages, and ensure any retained ResolutionPath guidance is clearly separated as an advanced or database-specific chapter.

Written by the indexing model from the issue text.

Description

documentation

Describe the bug
Now that specific nuget packages exist for each DB type, shouldn't the docs be updated to not use resolutionPath in the samples?

Of course another specific chapter about ResolutionPath could be added, but it shouldn't be the generic case anymore?

Dominant language
F#
Stars
627
Forks
147
Avg merge
2h 2m
Merged PRs (30d)
1

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.

More from fsprojects/SQLProvider

All issues in fsprojects/SQLProvider

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.