-
-
Notifications
You must be signed in to change notification settings - Fork 721
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
chore: milestone strategy tabs #8851
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
frontend/src/component/releases/ReleasePlanTemplate/MilestoneStrategyTitle.tsx
Outdated
Show resolved
Hide resolved
constraints: [], | ||
title: '', | ||
id: 'temp', | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this? If the only purpose is to fill the default values of a new strategy I think there are better options, like making this a responsibility of ReleasePlanTemplateAddStrategyForm
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll take another look at it, was a little annoying with all the strategy?.prop
everywhere. The other solution would be to add a route for it like we do in features, but I didn't want to mess around with route if I have a built template object in create waiting to be submitted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's okay, we can proceed with this for now and clean up later
Adding tabs and submit/save button to add strategy form