mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 06:25:54 +03:00
[PR #450] [MERGED] refactor:pass ctx to db layer, return err instead of recover panic #600
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#600
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/go-shiori/shiori/pull/450
Author: @hulb
Created: 7/10/2022
Status: ✅ Merged
Merged: 9/30/2022
Merged by: @fmartingr
Base:
master← Head:feat/pass-ctx-to-db📝 Commits (2)
4c74da2refactor:pass ctx to db layer, return err instead of recover panicb33aeedMerge branch 'feat/pass-ctx-to-db' into master-new📊 Changes
20 files changed (+875 additions, -702 deletions)
View changed files
📝
go.mod(+2 -1)📝
internal/cmd/add.go(+2 -2)📝
internal/cmd/check.go(+2 -2)📝
internal/cmd/delete.go(+1 -1)📝
internal/cmd/export.go(+1 -1)📝
internal/cmd/import.go(+9 -3)📝
internal/cmd/open.go(+1 -1)📝
internal/cmd/pocket.go(+9 -3)📝
internal/cmd/print.go(+1 -1)📝
internal/cmd/root.go(+12 -11)📝
internal/cmd/update.go(+4 -4)📝
internal/cmd/utils.go(+1 -1)📝
internal/database/database.go(+41 -17)📝
internal/database/mysql.go(+214 -205)📝
internal/database/pg.go(+217 -201)📝
internal/database/sqlite.go(+278 -215)📝
internal/webserver/handler-api-ext.go(+15 -6)📝
internal/webserver/handler-api.go(+52 -22)📝
internal/webserver/handler-ui.go(+12 -4)📝
internal/webserver/utils.go(+1 -1)📄 Description
This PR makes a refactor of ways to handle error in db layer. I don't think it's proper to panic when there is an error in db actions. And every db action should be executed with a context passed by the caller.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.