-
-
Notifications
You must be signed in to change notification settings - Fork 148
refactor: consolidate notifcation provider forms #1704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kmendell
wants to merge
1
commit into
main
Choose a base branch
from
refactor/consolidate-forms
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,669
−2,170
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 tasks
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
12 files reviewed, 3 comments
frontend/src/routes/(app)/settings/notifications/providers/NotificationProviderTestMenu.svelte
Show resolved
Hide resolved
1e1751a to
d95a8db
Compare
d446335 to
720bde2
Compare
9b2386d to
41efb69
Compare
720bde2 to
d68c3b0
Compare
getarcaneappbot
approved these changes
Feb 10, 2026
d68c3b0 to
9ee2012
Compare
41efb69 to
3d9f8f4
Compare
3d9f8f4 to
b930148
Compare
🔍 Deadcode AnalysisFound 1 unreachable functions in the backend. View detailsOnly remove deadcode that you know is 100% no longer used.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What This PR Implements
Related issue
Related Issue
Fixes #
Changes Made
Testing Done
./scripts/development/dev.sh startjust lint all)just test backendChecklist
mainbranchAI Tool Used (if applicable)
AI Tool:
Assistance Level:
What AI helped with:
I reviewed and edited all AI-generated output:
I ran all required tests and manually verified changes:
Additional Context
Disclaimer Greptiles Reviews use AI, make sure to check over its work.
To better help train Greptile on our codebase, if the comment is useful and valid Like the comment, if its not helpful or invalid Dislike
Greptile Overview
Greptile Summary
This PR refactors the notifications settings UI by consolidating the individual built-in provider forms into a schema-driven
BuiltInProviderForm+DynamicProviderFormBuilder, and introduces a reusableNotificationProviderTestMenudropdown. On the backend, Apprise test notifications are expanded to support multiple test payload types via a newtypequery parameter passed through the handler and intoAppriseService.TestNotification(ctx, testType).Key issues to address before merge:
onclickinstead of Svelteon:click, so selecting a test option won’t trigger....?type=${type}without URL-encoding, which can produce malformed requests iftypecontains reserved characters.typeand turns unsupported values into a 500; invalid client inputs should be handled as a 4xx (validate/normalizetypeat the boundary).Confidence Score: 3/5
NotificationProviderTestMenuevent binding will prevent tests from running, and the new query-param plumbing needs boundary validation/encoding to avoid malformed requests and incorrect 500s.Important Files Changed
typequery param for Apprise test; currently forwards unchecked values which can surface as 500s for invalid client input.typeparameter to Apprise test call but interpolates it into URL without encoding.onclickinstead of Svelteon:clickso options won't trigger.