-
Notifications
You must be signed in to change notification settings - Fork 41
FLUT-962617 - [Feature] UG content for Directional Zooming #1236
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
base: development
Are you sure you want to change the base?
FLUT-962617 - [Feature] UG content for Directional Zooming #1236
Conversation
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
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.
Fine
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
Feature description
Analysis and design
Followed the pinch zooming UG content and updated the directional zooming content.
Pending in adding API link for enableDirectionalZooming
Solution description
Updated content and code snippet for directional zooming in UG.
Output screenshots
Areas affected and ensured
No, areas affected.
API Changes
None.
Behavioral Changes
No behavioral changes.
Test cases
Provide the unit testing written file details to understand the use cases considered in this implementation.
If there is no TDD (if it’s not possible to follow), provide the UI automation script location and the Excel file that contains the use cases considered in this implementation.
Provide the test cases Excel file alone if the feature cannot be automated in any case.
List out all the scenarios you have tested after include these changes. You can refer the predefined scenarios from below link.
https://syncfusion.atlassian.net/wiki/display/CHARTXAMARIN/Chart+Test+Plan
Testbed sample location
Provide the test bed sample location where code reviewers can review the new feature’s behaviors. This depends on the CI process that your team follows. It can be from NPMCI, HockeyApp, staging site, local server, etc.
Does it have any known issues?
If this feature contains any known issues, provide the proper details about the issues.
Does it have memory leak?
Ensure the feature contains memory leak or not (if applicable).
MR CheckList