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: Enforce one dependency #4835

Merged
merged 8 commits into from
Sep 26, 2023
Merged

feat: Enforce one dependency #4835

merged 8 commits into from
Sep 26, 2023

Conversation

kwasniew
Copy link
Contributor

About the changes

Even though our DB supports multiple parent dependencies we want to start experimenting only with one. I'm removing all deps for a feature before creating a new one. Everything is part of the DB Tx started in the controller.

Important files

Discussion points

@vercel
Copy link

vercel bot commented Sep 26, 2023

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

2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Visit Preview Sep 26, 2023 0:04am
unleash-monorepo-frontend ⬜️ Ignored (Inspect) Visit Preview Sep 26, 2023 0:04am

@@ -60,11 +60,6 @@ beforeAll(async () => {
'featureY',
{ feature: 'featureX', variants: ['featureXVariant'] },
);
// depend on parent being disabled
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

currently we only support only one dependency in admin. Will bring this back when we support more than one.

@kwasniew kwasniew merged commit 76a2ec5 into main Sep 26, 2023
8 checks passed
@kwasniew kwasniew deleted the enforce-one-dependency branch September 26, 2023 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

2 participants