-
Notifications
You must be signed in to change notification settings - Fork 1
refactor(renderer): split AppContext and ConfigTab concerns #131
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
Merged
Mehdi-Bl
merged 4 commits into
main
from
feat/renderer-concern-split-appcontext-configtab
Feb 14, 2026
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
15090ee
refactor(renderer): split AppContext and ConfigTab concerns
Mehdi-Bl ba11135
fix(types): enforce typed config form field updates
Mehdi-Bl 1accf5a
fix(renderer): handle invalid yaml safely in config flows
Mehdi-Bl 51f249b
fix(security): avoid regex hotspot in api key redaction
Mehdi-Bl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
3. Parse errors reset form
🐞 Bug⛯ ReliabilityConfigTab’s load effect now uses parseConfigContent(), which catches YAML parse errors and returns {}. This means invalid YAML no longer triggers the surrounding try/catch path and instead reloads the form with defaults, clearing provider validation/test feedback and potentially confusing users while editing broken YAML.Agent Prompt
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools