Uh oh!
There was an error while loading. Please reload this page.
Reverted back Luma Ray Settings control - #316
Conversation
Important Review skippedAuto reviews are disabled on this repository. To trigger a review, include ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches✨ Simplify code
Comment |
There was a problem hiding this comment.
Pull request overview
This PR reverts the video edit “controls” typing/modeling in runware/types.py back to a flat-field representation on IVideoEditSettingsControls, removing the previously introduced per-control helper dataclasses and their dict→dataclass coercion.
Changes:
- Removed nested per-control dataclasses (
IVideoEditPoseControl,IVideoEditDepthControl, etc.). - Updated
IVideoEditSettingsControlsto use flat primitive fields (poseStrength,depthBlur,normalsAugmentation,trajectorySparsity,face). - Removed the per-field dict coercion previously performed in
IVideoEditSettingsControls.__post_init__.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Changed
IVideoEditSettingsControlsnow uses flat fields for edit controls instead of nested per-control dataclasses:poseStrength: Optional[str]depthBlur: Optional[float]normalsAugmentation: Optional[float]trajectorySparsity: Optional[float]face: Optional[bool]Removed
IVideoEditSettingsControlsfields:IVideoEditPoseControlIVideoEditDepthControlIVideoEditNormalsControlIVideoEditTrajectoryControlIVideoEditFaceControl