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
[ADF-5158] ECM Version Directive #5779
Conversation
} | ||
|
||
private initCompatibilityVersion() { | ||
this.discoveryApiService.getEcmProductInfo().toPromise().then( |
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.
don't use .toPromise
because it is deprecated and will be soon removed
I don't think "ECM" (enterprise content management) is the right term here, maybe "ACS" is better? |
Codecov Report
@@ Coverage Diff @@
## develop #5779 +/- ##
===========================================
+ Coverage 83.88% 83.93% +0.04%
===========================================
Files 960 963 +3
Lines 27164 27231 +67
Branches 3788 3798 +10
===========================================
+ Hits 22787 22855 +68
+ Misses 3247 3240 -7
- Partials 1130 1136 +6
Continue to review full report at Codecov.
|
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.
the documentation seems to be not update
aaea618
to
28fb5a2
Compare
1f8bd09
to
058f417
Compare
/rebase |
0f65480
to
252a549
Compare
I don't think you need to change the e2e they are working on develop |
252a549
to
1813ba4
Compare
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)
https://issues.alfresco.com/jira/browse/ADF-5158
What is the new behaviour?
This new directive allows component to hide when the app is not running the ACS version required for them to work properly.
This means this button will be present in the DOM tree from 6.0.0 onwards. Otherwise it will be removed to avoid the component breaking the app.
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: