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

chore: milestone strategy tabs #8851

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

daveleek
Copy link
Contributor

@daveleek daveleek commented Nov 25, 2024

Adding tabs and submit/save button to add strategy form

image

Copy link

vercel bot commented Nov 25, 2024

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

Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 25, 2024 2:49pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Visit Preview Nov 25, 2024 2:49pm

Copy link
Contributor

github-actions bot commented Nov 25, 2024

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

constraints: [],
title: '',
id: 'temp',
});
Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Approved PRs
Development

Successfully merging this pull request may close these issues.

2 participants