Handle responses with custom error #14

Open

let_rec wants to merge 8 commits from feat/handle_response into main

pull from: feat/handle_response

merge into: xinux:main

xinux:main

xinux:feat/general-report_lib

xinux:clippy

xinux:refactors

xinux:task/forgejo-ci-cd

xinux:feature/send-key

xinux:revert-24-error-handling

xinux:task/adding-time

xinux:feature/gpg-key-setup

xinux:encryption

xinux:rc-1

Conversation 0 Commits 8 Files changed 8 +176 -12

let_rec commented 2026-05-25 20:29:38 +00:00

Owner

Copy link

Summary

Now relago can handle server's responses and show related message for user.

Motivation

Relago lacked a handler for handling errors such as invalid request, server problem and so on.

What have I done

• We made requests to the server and even received what we wanted, our functions worked correctly. However, we didn't foresee any problems that could arise from requests. So, we didn't have any request handlers, so I created a new custom error handler using enum and thiserror.
• Now, if the user doesn't have a file with identifiers or has accidentally deleted it, a new button is displayed on the graphical interface for creating it and then generating a report.

This PR solves this issue - closes #13

## Summary Now relago can handle server's responses and show related message for user. ### Motivation Relago lacked a handler for handling errors such as invalid request, server problem and so on. ### What have I done - We made requests to the server and even received what we wanted, our functions worked correctly. However, we didn't foresee any problems that could arise from requests. So, we didn't have any request handlers, so I created a new custom error handler using enum and thiserror. - Now, if the user doesn't have a file with identifiers or has accidentally deleted it, a new button is displayed on the graphical interface for creating it and then generating a report. This PR solves this issue - closes #13

let_rec added 3 commits 2026-05-25 20:29:38 +00:00

chore: change copied idfile name user to uuid aa7664fc1b

chore: change default value for data_dir db5fa2be63

feat: created custom error enum for handle responses e169ff957b

let_rec added 1 commit 2026-05-25 20:32:32 +00:00

fix: import thiserror from workspace e6cce7a8ef

let_rec added 1 commit 2026-05-25 20:35:38 +00:00

chore: use custom errors for upload function 0a525f566e

let_rec added 1 commit 2026-05-25 20:50:07 +00:00

feat: create new function for run setup-key 4e07762c21

let_rec added 1 commit 2026-05-25 20:54:34 +00:00

feat: the gui has been updated, if user doesn't have ID, a new button is displayed to launch run setup-key func 2d94426257

let_rec added 1 commit 2026-05-25 20:55:44 +00:00

fix: when user doesn't have ID new button doesn't displayed 5acadbfbe1

let_rec 2026-05-25 21:00:38 +00:00

• added the
  enhancement
  label
• requested review from lambdajon

let_rec self-assigned this 2026-05-25 21:01:00 +00:00

Some checks failed

Hide all checks

Test CI / test-flake (push) Successful in 12s

Details

Test CI / test-project (push) Failing after 1m38s

Details

Test CI / test-flake (pull_request) Successful in 11s

Details

Test CI / test-project (pull_request) Failing after 8s

Details

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feat/handle_response:feat/handle_response

git switch feat/handle_response

Merge

Merge the changes and update on Forgejo.

git switch main

git merge --no-ff feat/handle_response

git switch feat/handle_response

git rebase main

git switch main

git merge --ff-only feat/handle_response

git switch feat/handle_response

git rebase main

git switch main

git merge --no-ff feat/handle_response

git switch main

git merge --squash feat/handle_response

git switch main

git merge --ff-only feat/handle_response

git switch main

git merge feat/handle_response

git push origin main

Sign in to join this conversation.

Reviewers

No reviewers

lambdajon

Labels

Clear labels

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

fix

fixing good

  

good first issue

  

help wanted

Need some help

  

question

More information is needed

  

wontfix

This won't be fixed

No labels

bug

duplicate

enhancement

fix

good first issue

help wanted

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

let_rec

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

xinux/relago!14

No description provided.