-
Notifications
You must be signed in to change notification settings - Fork 14
Migrating to sql-alchemy 2.0 - Better typing support in the ORM #2769
Copy link
Copy link
Open
Labels
kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/stack-guidanceCategorizes an issue or PR as relevant to SIG Stack Guidance.Categorizes an issue or PR as relevant to SIG Stack Guidance.
Description
Metadata
Metadata
Assignees
Labels
kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/stack-guidanceCategorizes an issue or PR as relevant to SIG Stack Guidance.Categorizes an issue or PR as relevant to SIG Stack Guidance.
Type
Projects
Status
📋 Backlog
Problem statement
Better typing is better code
High-level Goals
In so many words, fully typed ORM support (see 2.0 Features
Additional context
We also in storages (see graph/ in particular ) a lot of code which replicates sql-alchemy methods. This is the occasion to get rid of those.
Acceptance Criteria