upcoming: [M3-8025] - Placement Groups: Allow null for maximum_pgs_per_customer#10433
upcoming: [M3-8025] - Placement Groups: Allow null for maximum_pgs_per_customer#10433abailly-akamai merged 5 commits intolinode:developfrom
Conversation
|
Coverage Report: ✅ |
mjac0bs
left a comment
There was a problem hiding this comment.
The code and test coverage makes sense, so approving so as to make sure it gets in the upcoming release. I'm not a big fan of the text wrapping and way that unlimited is isolated on a line by itself, which makes it not very scannable and seem out of place.
I don't know that breaking the helper text earlier on that line would improve things, though, so maybe the lonely 'unlimited' is the best we can do, short of rendering a different sentence for the unlimited case, and my guess is that UX considered that and opted not to.
|
@mjac0bs i completely agree - i made an executive decision to shorten that sentence which was too verbose anyway. (screenshot updated) |


Description 📝
maximum_pgs_per_customer: This value can be unlimited for some customers in some regions, for which the API returns thenullvalue. The UI representation of thisnullvalue is the "unlimited" stringChanges 🔄
nullformaximum_pgs_per_customerin APIv4Target release date 🗓️
5/13/2024
Preview 📷
How to test 🧪
Verification steps
ℹ️ have both the "Placement Group" feature flag and MSW on
As an Author I have considered 🤔
Check all that apply