TL;DR
Stub for sub-task 2 of the cross-repo rename tracked in FreeshardBase/freeshard-controller#236. The field Profile.delete_after actually means "stop after" — the controller stops shards on this date; deletion is separate.
Depends on: FreeshardBase/freeshard-controller#236 sub-task 1 (controller-side rename + OpenAPI regen).
Blocks: FreeshardBase/web-terminal#21.
Scope
- Run
just get-types to pull the renamed stop_after field from the controller's regenerated OpenAPI.
- Rename
shard_core/data_model/profile.Profile.delete_after → stop_after.
- Update
Profile.from_shard() mapping.
- Search for any other references to
delete_after in shard_core/ (none expected) and rename if found.
- Run
just cleanup.
Acceptance criteria
See the tracking issue for the full rationale and context: FreeshardBase/freeshard-controller#236.
TL;DR
Stub for sub-task 2 of the cross-repo rename tracked in FreeshardBase/freeshard-controller#236. The field
Profile.delete_afteractually means "stop after" — the controller stops shards on this date; deletion is separate.Depends on: FreeshardBase/freeshard-controller#236 sub-task 1 (controller-side rename + OpenAPI regen).
Blocks: FreeshardBase/web-terminal#21.
Scope
just get-typesto pull the renamedstop_afterfield from the controller's regenerated OpenAPI.shard_core/data_model/profile.Profile.delete_after→stop_after.Profile.from_shard()mapping.delete_afterinshard_core/(none expected) and rename if found.just cleanup.Acceptance criteria
Profile.stop_afterreplacesProfile.delete_after.delete_afterreferences inshard_core/.See the tracking issue for the full rationale and context: FreeshardBase/freeshard-controller#236.