Refactor: Implement Strategy pattern for params and study key handling#702
Refactor: Implement Strategy pattern for params and study key handling#702
Conversation
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Refactored ParamMixin and endpoint parameter processing to use the Strategy pattern.
StudyKeyStrategyprotocol with implementations:PopStudyKeyStrategy,KeepStudyKeyStrategy,OptionalStudyKeyStrategy.MappingParamProcessorfor declarative parameter mapping.UsersEndpointandRecordsEndpointto use new strategies, removing ad-hoc processor classes and boolean flags.validate_record_entrylogic toimednet/validation/cache.pyto improve cohesion.StudiesEndpointto useOptionalStudyKeyStrategy.PR created automatically by Jules for task 10998208052101135393 started by @fderuiter