Carpenteri1 / Carpenteri1/Gridly

Move to Entity Framework core

Open
#305 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
1
Forks
0
Avg merge
1h 12m
Merged PRs (30d)
27

Description

## What
Move away from Dapper to

## Why
To get away from the bloat, streamline queries and make the more readable.

# Definition of done
- [ ] Clean up handler
- [ ] Make one save not multiple in handler
- [ ] Create Extensions for queries and commands if needed
- [ ] Create Service for query and commands if needed
- [ ] Make sure All endpoints works as intended
- [ ] Make sure tests work as intended
- [ ] Remove Dapper package
- [ ] Remove Repositories

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the handlers, repositories, endpoints, tests, and current Dapper usage mentioned in the issue. Map how queries and commands currently save data before deciding whether extensions or services are needed. Done means all endpoints and tests still work, handlers perform one save, Dapper and repositories are removed, and the Entity Framework Core migration is complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend, database
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.