-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat(operator): Add Org DeleteOn
and Account CancelledAt
dates
#6736
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,6 +20,11 @@ const AccountGrid: FC = () => { | |
return account?.marketplaceSubscription?.subscriberId ?? 'N/A' | ||
} | ||
|
||
const cancelledAt = account?.cancelledAt | ||
? new Date(account?.cancelledAt) | ||
: null | ||
const hasCancelledAt = Boolean(cancelledAt) | ||
|
||
return ( | ||
<FlexBox | ||
direction={FlexDirection.Row} | ||
|
@@ -47,6 +52,15 @@ const AccountGrid: FC = () => { | |
body={organizations?.[0]?.provider ?? 'N/A'} | ||
testID="cloud-provider" | ||
/> | ||
<AccountField | ||
header="Cancelled At" | ||
body={ | ||
account.type === 'cancelled' && hasCancelledAt | ||
? `${cancelledAt.toLocaleTimeString()} ${cancelledAt.toDateString()}` | ||
: 'N/A' | ||
} | ||
testID="cancelled-at" | ||
/> | ||
</FlexBox> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks good; but if you change anything based on the above comment, this component should have the same logic. 👍 |
||
<FlexBox | ||
direction={FlexDirection.Column} | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One possibility here is that the
deleteOn
string exists but isn't valid, sonew Date
evaluates toNaN
. That would cause any methods chained off deleteOn to fail, but you should be fine here since[whatever conditions] && NaN
is falsy, so the code that relies on those chained methods will not render.What could be more explicit (and defer to you on which you prefer) would be to separate the variable that gates whether to render the data from the data that is being rendered, so that we know the rendering condition can only be
true
orfalse
.And then make the condition for rendering
hasDeleteDate
But up to you - I've done some testing here and both should have the same effect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I think that's probably a good change. Plus
hasDeleteDate
is a better name for a rendering condition than just the truthiness ofdeleteOn