feat: new parseConfiguration for error feedback #41
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.
Stacked onto #35
Summary
This PR introduces a new
parseConfiguration()convenience function that provides comprehensive error feedback when parsing flag configurations and bandit models. The new API replaces the previousfrom_jsonpattern with explicit error tracking, making it easier to diagnose configuration issues.What Changed
New Public API
Added
parseConfiguration()convenience function with two overloads:Key Features
Breaking Changes
- Old: BanditResponse response = json_object;
- New: BanditResponse response = internal::parseBanditResponse(jsonStr, error);
- Provides error tracking and better diagnostics
- parseConfigResponse() → internal::parseConfigResponse()
- parseBanditResponse() → internal::parseBanditResponse()
- These are now implementation details; use parseConfiguration() instead
Migration Guide
Before:
After: