feat: add default location column to server type table#1340
feat: add default location column to server type table#1340
Conversation
|
I don't know if this is really pretty, maybe there is a better way to display this information. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1340 +/- ##
=======================================
Coverage 72.56% 72.57%
=======================================
Files 300 300
Lines 10986 10990 +4
=======================================
+ Hits 7972 7976 +4
Misses 2125 2125
Partials 889 889
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
As we only have had |
Yes, I am happy with this idea, unless you think its too big of a change. Update the description to show the new output. |
3042b60 to
578190a
Compare
|
|
I think, unless explicitly stated, those locations always refer to "supported" and not "available". So availability will only be printed in the describe function. We would revisit this once we receive more information from the API.
Not a fan, it adds a level of indirection. If we end up with too many location maybe it will make sens, but until then I think its ok? |
Adds a default
locationcolumn to display in which location a server type is supported:Related to #1322