fix-exui-1175-Complex fields not being unhidden by Show Conditions #1642
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
RiteshHMCTS
changed the title
RiteshHMCTS
changed the base branch from
exui-1175-new-base-branch
to
master
|
OgunyemiO
approved these changes
Dec 15, 2023
kasi-subramaniam
approved these changes
Dec 15, 2023
Daniel-Lam
added a commit
that referenced
this pull request
Jan 16, 2024
* EUI-6645 Restricted case acceess * EUI-6645 Restricted case acceess * EUI-6645 Restricted case access * update version * install * Add translation package * update version * Update package * yarn install * Update package * Merge from master * Merge from master * Merge from master * Merge from master * Merge from master * EUI-8816 Restricted Case Access - Feature toggle for deployment to Production * EUI-8816 Restricted Case Access - Feature toggle for deployment to Production * EUI-8816 Restricted Case Access - Feature toggle for deployment to Production * Update package version * version update after merge from base branch * EUI-8816 Restricted case access feature toggle functionality * Upgrade to Node-18 and NG-15 (#1550) * kick-off node 18 upgrade * use pay component at local * ng update @angular/core@12 @angular/cli@12 --force * ng update @angular/material@12 --force * ng update @angular/core@13 @angular/cli@13 --force * ng update @angular/material@13 --force * ng update @angular/core@14 @angular/cli@14 --force * cdk 14 * ts version * upgraes for fix * upgrade rpx-xui-translation * upgrade yargs-parser * upgrade cli to 15 * fix damn ng breakdown * ng update @angular/material@14 --force * ng update @angular/core@15 @angular/cli@15 --force * ng update @angular/material@15 --force * correct compilation errors after upgrades * ignore angular cache * set new major version * add yarn release file * comment out broken lint task * temporarily use ccpay-component from local * fix tests * fix tests * upgrade to media viewer pre-release * update version tag * delete local ccpay dist folder * use ccpay component prerelease * skip the tasks (to be fixed later on) * remove steps to unblock pre-release * use node 14 for release * Code tide * package json update * fix update package.json file and code tidy * fix update package.json file * fix update package.json file and code tidy * package.json file update * Using legacy angular material * package.json version update * fix: EXUI-787 - Fixed lint srcipt, lint issues, code issue. Code tidy * updated codebase * fix: EXUI-790 unit test now working; EXUI-996- Fixed dateTime Picker; Fix issue probate buttons - cancel and continue button * package.json updated * Update typography.scss * Version update * Update npmpublish.yml * update polling service inline with sonarcloud - Security Hotspot * code tidy * added updated fork version of rx-polling library * fix - EXUI-996 - fix issue with incorrect date formate * App version updated and code tidy * Update RELEASE-NOTES.md * version update * Update case-file-view-folder.component.ts * Vesion update * update test and karma config * Update karma.conf.js * Update case-file-view-folder-selector.component.spec.ts * ccpay-web-component version updated * version update * fix broken functional test and update toolkit version * version update * rpx-xui-translation version update - 1.0.1 * @olusegz07 rpx-xui-translation version update - 1.0.2 --------- Co-authored-by: olusegun odunukan <olusegun.odunukan@hmcts.net> Co-authored-by: Olu <142989683+olusegz07@users.noreply.github.com> * fix yarn audit issue (#1634) * fix yarn audit issue * yarn audit fix yarn audit fix * Update RELEASE-NOTES.md * Fix/ex UI 1151 yarn audit version (#1637) * fix yarn audit issue * yarn audit fix yarn audit fix * Update RELEASE-NOTES.md * Version updated * fix-exui-1175-Complex fields not being unhidden by Show Conditions (#1642) * fix-exui-1175 * exui-1105-avoid judicial user from hidden * Defensive coding for HIDDEN_TEMP * setting display_context as HIDDEN_TEMP * version updated * Add util function to check for valid complex types * version updated --------- Co-authored-by: Andy Wilkins <andy.wilkins@hmcts.net> --------- Co-authored-by: John Benjamin <john.benjamin@hmcts.net> Co-authored-by: David Rajkumar Jayakumar <107850923+DavidJayakumar@users.noreply.github.com> Co-authored-by: DavidJayakumar <David.Jayakumar@hmcts.net> Co-authored-by: John Benjamin <90200268+johnbenjamin-hmcts@users.noreply.github.com> Co-authored-by: codaimaster <55559010+codaimaster@users.noreply.github.com> Co-authored-by: olusegun odunukan <olusegun.odunukan@hmcts.net> Co-authored-by: Olu <142989683+olusegz07@users.noreply.github.com> Co-authored-by: RiteshHMCTS <74713687+RiteshHMCTS@users.noreply.github.com> Co-authored-by: Andy Wilkins <andy.wilkins@hmcts.net>
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.
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/EXUI-1175
https://tools.hmcts.net/jira/browse/EXUI-1105
Change description
Complex fields not being unhidden by Show Conditions
Does this PR introduce a breaking change? (check one with "x")