Skip to content
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

feat: v2 migration #116

Merged
merged 27 commits into from
Oct 16, 2024
Merged

feat: v2 migration #116

merged 27 commits into from
Oct 16, 2024

Conversation

WhyAsh5114
Copy link
Owner

@WhyAsh5114 WhyAsh5114 commented Oct 14, 2024

Description

Stuff regarding V2 migration work, almost done with V3 now, let's go! Fixes #109.

Type of change

  • New feature (non-breaking change which adds functionality)

Tasklist

  • migration tRPC implementation
  • fix data losses: rest days
  • figure out mesocycle start and end dates
  • bodyweight exercises not being migrated as bodyweight exercises in MesocylceExerciseTemplate
  • add input to take average workout time to improve workout duration assumption
  • remove (or at least improve) bodyweight assumption, use input during migration if not available in v2
  • or mark user as migrated from v2 to prevent multiple duplicate migrations?

Won't be doing

  • allow active mesocycle (should be either on v2 OR v3, NOT on both)
  • give option for v2 migration in Getting started component? (maybe)

V2 task

  • add v3 banner in v2 with migration guide

Copy link

vercel bot commented Oct 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
my-fit-jgqg ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 16, 2024 11:16am

@WhyAsh5114 WhyAsh5114 changed the title 109 v2 migration feat: v2 migration Oct 14, 2024
@WhyAsh5114 WhyAsh5114 self-assigned this Oct 14, 2024
@WhyAsh5114 WhyAsh5114 added the v3-enhancement New feature or request for v3 label Oct 14, 2024
@WhyAsh5114 WhyAsh5114 added this to the v3-stable milestone Oct 14, 2024
@WhyAsh5114 WhyAsh5114 marked this pull request as ready for review October 16, 2024 11:15
@WhyAsh5114 WhyAsh5114 merged commit ffd5494 into main Oct 16, 2024
6 checks passed
@WhyAsh5114 WhyAsh5114 deleted the 109-v2-migration branch October 16, 2024 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v3-enhancement New feature or request for v3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

V2 Migration
1 participant