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

fix: stickiness #3471

Merged
merged 10 commits into from
Apr 6, 2023
Merged

fix: stickiness #3471

merged 10 commits into from
Apr 6, 2023

Conversation

andreas-unleash
Copy link
Contributor

  • Fixes project model/store
  • Fixes UI sync issues when switching stickiness

About the changes

Closes #

Important files

Discussion points

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@vercel
Copy link

vercel bot commented Apr 6, 2023

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

Name Status Preview Comments Updated (UTC)
unleash-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 6, 2023 2:09pm
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 6, 2023 2:09pm

@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

@andreas-unleash
Copy link
Contributor Author

andreas-unleash commented Apr 6, 2023

null checks failing is expected - its comparing with main

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Copy link
Contributor

@kwasniew kwasniew left a comment

Choose a reason for hiding this comment

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

Non blocking approve with a few comments left

@@ -308,14 +314,13 @@ export const EnvironmentVariantsModal = ({
}, [apiPayload.error]);

const handleClose = () => {
updateStickiness(defaultStickiness).catch(console.warn);
updateStickiness(defaultStickiness).then();
Copy link
Contributor

Choose a reason for hiding this comment

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

empty then left

@kwasniew
Copy link
Contributor

kwasniew commented Apr 6, 2023

One more thing. This PR increases the number of null check errors from 397 to 401. Since we're trying to bring this number down to 0 I'd try to keep the number same or even lower by paying down some tech debt.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Signed-off-by: andreas-unleash <andreas@getunleash.ai>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

After enabling strictNullChecks this PR would be increasing the number of null check errors from 397 to 401.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

@andreas-unleash andreas-unleash changed the base branch from 4.22 to main April 6, 2023 14:11
@andreas-unleash andreas-unleash changed the base branch from main to 4.22 April 6, 2023 14:14
@andreas-unleash andreas-unleash merged commit 92328f6 into 4.22 Apr 6, 2023
9 of 14 checks passed
@andreas-unleash andreas-unleash deleted the tmp-4.22.3 branch April 6, 2023 14:17
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