-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add logic to change browser state #26763
Comments
astone123
changed the title
Add mutation to change browser state
Add logic to change browser state
May 16, 2023
Hey team! Please add your planning poker estimate with Zenhub @jordanpowell88 @lmiller1990 @marktnoonan @mike-plummer @warrensplayer @dkasper-was-taken |
dkasper-was-taken
added a commit
that referenced
this issue
May 30, 2023
1 task
dkasper-was-taken
added a commit
that referenced
this issue
Jun 2, 2023
* chore: add browser state action for debug (#26763) * Address PR comments - remove unneeded async and test context - genericize openProject function * Revert route change, update spec description
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to switch to the debug page for a specific run when the user clicks a notification, we need to be able to do two things programmatically:
Add ways to make this happen in the data-context layer.
Note: A path for this already exists specifically for switching between specs - this can likely be copied & adjusted as needed. See
packages/server/lib/makeDataContext.ts
:projectApi.runSpec
& the function it calls. This is being added/updated in #26782The text was updated successfully, but these errors were encountered: