[HXCS-2818] - fix issues with ERROR RangeError: Invalid time value #9340
Conversation
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
dominikiwanekhyland
requested review from
eromano,
popovicsandras and
DenysVuika
as code owners
dominikiwanekhyland
force-pushed
the
HXCS-2818-when-i-set-in-workspace-just-date-for-the-date-property-also-time-is-set-fix
branch
from
9fbfb3e to
90b43da
Compare
wideLandscape
approved these changes
Feb 16, 2024
dominikiwanekhyland
force-pushed
the
HXCS-2818-when-i-set-in-workspace-just-date-for-the-date-property-also-time-is-set-fix
branch
from
90b43da to
18bf5d7
Compare
dominikiwanekhyland
force-pushed
the
HXCS-2818-when-i-set-in-workspace-just-date-for-the-date-property-also-time-is-set-fix
branch
from
18bf5d7 to
20b314a
Compare
|
dominikiwanekhyland
deleted the
HXCS-2818-when-i-set-in-workspace-just-date-for-the-date-property-also-time-is-set-fix
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
There are errors in the console when opening the details tab for record files in ADW and they are not rendered correctly. Errors:
core.mjs:7626 ERROR RangeError: Invalid time value
at lightFormat (index.js:80:11)
at DateFnsUtils.forceLocal (adf-core.mjs:1846:36)
at CardViewDateItemModel.prepareDate (adf-core.mjs:16821:52)
at get displayValue (adf-core.mjs:16812:43)
at adf-content-services.mjs:19853:89
at Array.filter ()
at ContentMetadataComponent.showGroup (adf-content-services.mjs:19853:45)
at ContentMetadataComponent_ng_container_5_div_1_Template (adf-content-services.mjs:19986:13666)
at executeTemplate (core.mjs:12108:9)
at refreshView (core.mjs:11971:13)
at toDate (index.js:48:20)
at lightFormat (index.js:78:28)
at DateFnsUtils.forceLocal (adf-core.mjs:1846:36)
at CardViewDateItemModel.prepareDate (adf-core.mjs:16821:52)
at get displayValue (adf-core.mjs:16812:43)
at adf-content-services.mjs:19853:89
at Array.filter ()
at ContentMetadataComponent.showGroup (adf-content-services.mjs:19853:45)
at ContentMetadataComponent_ng_container_5_div_1_Template (adf-content-services.mjs:19986:13666)
at executeTemplate (core.mjs:12108:9)
What is the new behaviour?
Details tab is rendered correctly and there are no errors in the console.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: