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

Handle undefined assetChecksAvailable in current session #17170

Merged
merged 3 commits into from
Oct 12, 2023

Conversation

salazarm
Copy link
Contributor

Summary & Motivation

If you access a session from localStorage from before this release then this property won't exist. We correctly use the existential operator (?.) in other places but looks like we forgot to use it here.

How I Tested These Changes

  1. Switched to release-1.5.2
  2. Made a new launchpad config
  3. Switched back to release-1.5.3 and saw the error:
  4. Screenshot 2023-10-11 at 11 28 22 PM
  5. Switched to this branch and saw the error go away

@github-actions
Copy link

github-actions bot commented Oct 12, 2023

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-9ur45e9m7-elementl.vercel.app
https://salazarm-assetChecksAvailable.core-storybook.dagster-docs.io

Built with commit 5c6e167.
This pull request is being automatically deployed with vercel-action

@salazarm salazarm merged commit 7f7eff5 into master Oct 12, 2023
@salazarm salazarm deleted the salazarm/assetChecksAvailable branch October 12, 2023 03:50
salazarm added a commit that referenced this pull request Oct 12, 2023
## Summary & Motivation

If you access a session from localStorage from before this release then
this property won't exist. We correctly use the existential operator
(?.) in [other places
](https://github.com/dagster-io/dagster/blob/45c5a47480b8f712d5c4c51e74213626d5061b79/js_modules/dagster-ui/packages/ui-core/src/launchpad/LaunchpadSession.tsx#L209)but
looks like we forgot to use it here.

## How I Tested These Changes

1. Switched to release-1.5.2
2. Made a new launchpad config
3. Switched back to release-1.5.3 and saw the error:
4. <img width="1164" alt="Screenshot 2023-10-11 at 11 28 22 PM"
src="https://github.com/dagster-io/dagster/assets/2286579/bfdec5bf-241d-429c-b64b-e4cae1f478da">
5. Switched to this branch and saw the error go away
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants