Repository navigation
fix: escape update-provider values and harden legacy provider recovery #25
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
ymkiux
merged 27 commits into
SakuraByteCore:main
from
SurviveM:fix/provider-section-safety
Mar 21, 2026
Merged
Changes from 3 commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
898ccfe
fix: escape update-provider values and avoid nested provider promotion
SurviveM f37932d
fix: rewrite update-provider fields as safe TOML strings
SurviveM ee7d0f6
fix: preserve inline comments when updating provider fields
SurviveM c1dd4f0
refactor: share TOML field replacement logic in cmdUpdate
SurviveM d700c98
fix: require provider-specific keys for nested legacy recovery
SurviveM 51fc4e2
fix: skip metadata tables in nested provider recovery
SurviveM 0069b97
fix: preserve dotted nested provider names in recovery
SurviveM 5d39be9
fix: keep raw legacy section path for nested providers
SurviveM e6f416e
fix: match legacy provider sections by parsed key semantics
SurviveM 58038f3
fix: disambiguate nested legacy provider section targeting
SurviveM 35a00ec
fix: attach exact legacy segments for direct providers
SurviveM 71aef30
fix: make exact section targeting exclusive in legacy updates
SurviveM db4bbdb
fix: recover name-only legacy nested providers and tighten e2e checks
SurviveM a9ce741
test: verify multiline rewrite via fresh cli parse
SurviveM 97a71cf
fix: append missing provider fields during legacy update
SurviveM 76ef036
fix: recover providers under top-level metadata namespace
SurviveM 53598ba
fix: handle escaped triple quotes in multiline provider fields
SurviveM b2ef52a
test: add TOML parse assertions for provider update e2e cases
SurviveM a1f3d8b
fix: handle literal triple-quoted strings in provider update
SurviveM 80aedcb
fix: handle escaped quote before multiline close delimiter
SurviveM d3010e8
fix: ignore multiline-string content in section range scan
SurviveM ccef5e3
fix: recurse after recovering nested legacy providers
SurviveM 569f220
fix: block unsafe fallback rewrites for multiline values
SurviveM 092c8d6
fix: skip multiline-string matches in field rewrite
SurviveM 0ffd919
fix: delete descendant provider sections with parent
SurviveM 337041b
fix: harden legacy provider collision and delete handling
SurviveM a2fee08
fix: drop metadata placeholders and preserve CRLF rewrites
SurviveM 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
Some comments aren't visible on the classic Files Changed page.
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
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.
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.
Uh oh!
There was an error while loading. Please reload this page.