Expose updated_at detail and render correctly #744
Merged
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.
Fixes #737
Some 'updated_at' values were not being exposed for some resources by the backend, which means:
undefined
dayjsOrNull(date)
function fails since the date value isundefined
, and function checks fornull
onlySolution is to ensure we expose
updated_at
when we intend to use/render it, and usedayjsOrNull
in the frontend to render the value correctly.Also removes 'updated at' field from the organization page membership related list. Don't think we need it there.