split out pool detailed info into a standalone settings page#26805
split out pool detailed info into a standalone settings page#26805
Conversation
|
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit bec08b1. |
18c1cfc to
c01da8d
Compare
c5aaa65 to
d269905
Compare
c01da8d to
15bc61b
Compare
d269905 to
05cbe94
Compare
15bc61b to
81fd01b
Compare
05cbe94 to
f508458
Compare
81fd01b to
948ce8f
Compare
f508458 to
36ef1c1
Compare
948ce8f to
e95b257
Compare
36ef1c1 to
4eb991b
Compare
e95b257 to
02311b6
Compare
4eb991b to
b50b563
Compare
02311b6 to
fd552b6
Compare
b50b563 to
53edb22
Compare
fd552b6 to
f1ee75f
Compare
87c0a6f to
d24cf46
Compare
f1ee75f to
3c5deda
Compare
d24cf46 to
80d3b13
Compare
3c5deda to
9fa4539
Compare
c3e9fa3 to
7d4debd
Compare
9fa4539 to
16f3f44
Compare
7d4debd to
7903c5f
Compare
47d228f to
0af051b
Compare
fefe7fa to
fda08ba
Compare
0af051b to
d199ebd
Compare
39f76f5 to
dd164aa
Compare
d199ebd to
8c0784c
Compare
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
3e86416 to
3f350c4
Compare
8c0784c to
f9a9f32
Compare
44a9628 to
30ce73f
Compare
f9a9f32 to
c72a8e6
Compare
30ce73f to
49a6f83
Compare
c72a8e6 to
7b80a1d
Compare
49a6f83 to
9f644f3
Compare
7b80a1d to
1ed7d4d
Compare
hellendag
left a comment
There was a problem hiding this comment.
Can you include a few screenshots?
| key={item.key} | ||
| item={item} | ||
| active={item.type === 'link' && pathname === item.path} | ||
| active={item.type === 'link' && pathname.startsWith(item.path)} |
There was a problem hiding this comment.
I wanted the Concurrency tab to selected when viewing the detailed page. The link item maps to the index page (without the specific key path).
| <InstanceHealthPageContent /> | ||
| </Route> | ||
| <Route path="/deployment/concurrency"> | ||
| <Route path="/deployment/concurrency(/?.*)"> |
There was a problem hiding this comment.
Could this be /deployment/concurrency/:concurrencyKey?? Or is the concurrencyKey value too complex for this?
There was a problem hiding this comment.
I wanted the URL to match both the top-level /deployment/concurrency url as well as the detailed pool-specific /deployment/concurrency/foo url.
There was a problem hiding this comment.
I was thinking that using :concurrencyKey? (with the ?) would allow this, but off the top of my head I don't remember whether that's the way to do that with react-router.
There was a problem hiding this comment.
oh, you're right, that does work
| > | ||
| <Subheading>In progress</Subheading> | ||
| </Box> | ||
| <Box style={{marginLeft: -1}}> |
There was a problem hiding this comment.
What does it look like without these?
There was a problem hiding this comment.
There's a left-border for all the table rows, so it looks like an extra thick border. I couldn't figure out how to disable that, so I just cheated 😭
There was a problem hiding this comment.
Yeah, I guess we have that elsewhere too. Oh well. Probably worth it for me to go in and fix these.
Could have sworn we had resolved that in some way at some point, since all of our tables tend to be full-width...
| if (String(value) !== concurrencyLimit.trim()) { | ||
| return false; | ||
| } |
There was a problem hiding this comment.
What's the specific case here?
There was a problem hiding this comment.
I think if you tried to do some sort of decimal:
const valueStr = "1.3";
const value = parseInt(valueStr); // evaluates to 1
There was a problem hiding this comment.
I think if you use type="number" on the input, it won't allow a decimal to be entered since the default stepping value is 1 and input is therefore restricted to integers.
9f644f3 to
9c9353d
Compare
1ed7d4d to
47a0fa5
Compare
| <InstanceHealthPageContent /> | ||
| </Route> | ||
| <Route path="/deployment/concurrency"> | ||
| <Route path="/deployment/concurrency(/?.*)"> |
There was a problem hiding this comment.
I was thinking that using :concurrencyKey? (with the ?) would allow this, but off the top of my head I don't remember whether that's the way to do that with react-router.
| > | ||
| <Subheading>In progress</Subheading> | ||
| </Box> | ||
| <Box style={{marginLeft: -1}}> |
There was a problem hiding this comment.
Yeah, I guess we have that elsewhere too. Oh well. Probably worth it for me to go in and fix these.
Could have sworn we had resolved that in some way at some point, since all of our tables tend to be full-width...
| <Heading> | ||
| <Box flex={{direction: 'row', gap: 8, alignItems: 'center'}}> | ||
| <div> | ||
| <Link to="/deployment/concurrency"> | ||
| {flagPoolUI ? 'Pools' : 'Concurrency keys'} | ||
| </Link> | ||
| </div> | ||
| <div>/</div> | ||
| <div>{concurrencyKey}</div> | ||
| </Box> | ||
| </Heading> |
There was a problem hiding this comment.
From the screenshot, this heading section looks like it needs a bottom border.
| if (String(value) !== concurrencyLimit.trim()) { | ||
| return false; | ||
| } |
There was a problem hiding this comment.
I think if you use type="number" on the input, it won't allow a decimal to be entered since the default stepping value is 1 and input is therefore restricted to integers.


Summary & Motivation
With #26804, we're directing more attention to the settings for specific pools.
This PR creates a new dedicated view for specific pool information (was previously in a dialog).
Screen.Recording.2025-01-23.at.11.16.45.AM.mov
How I Tested These Changes
BK
Changelog
Creates a standalone view for specific pool info