mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 23:25:52 +03:00
[GH-ISSUE #1093] [Enhancement] Refactoring user settings parsing #3040
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#3040
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?
Originally created by @koszeggy on GitHub (Mar 20, 2022).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1093
Originally assigned to: @koszeggy on GitHub.
Parsing user settings is a pain now as whenever a new enum or nullable type is used it must be handled manually.
A need for refactoring is also indicated in the source code:
As I mentioned I already addressed the issue during the development of #1069 because it affected my changes as well. But since the solution was dependent on #1069 (because I created a sub-branch from its feature branch and because it uses one of the libraries that was added for #1069) I waited with a new pull request until #1069 was merged.
Git was a bit confused though when I tried to merge the refactoring branch to
devbecause all of the changes of #1069 appeared again for review (even though these changes are merged now intodev), so in the end I canceled the pull request. I can try it again during the next week by creating a new branch directly fromdevand reintroducing the changes (onlyUserSettings.csis affected) so it will be clean enough for git, too.Until then, feel free to assign the issue to me.