-
Notifications
You must be signed in to change notification settings - Fork 459
[dev-v5] Migrate PullToRefresh component #4459
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
[dev-v5] Migrate PullToRefresh component #4459
Conversation
vnbaaij
left a comment
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.
Think this is pretty good already. Thanks!
Need to take a closer look at a pc still
examples/Demo/FluentUI.Demo.Client/Documentation/Components/PullToRefresh/PullToRefresh.md
Outdated
Show resolved
Hide resolved
|
@PascalVorwerk we have a line coverage threshold set of 98%. For this PR the percentage is now at 97.3%. So, the build action here on GitHub fails. The coverage for the PullToRefresh is only at 37% so a lot more tests are needed... You can generate a coverage report with the |
Yep i noticed haha, i was working in Rider and sadly don't have .dotCover, but working in vs code it gives me a better idea of where i am still missing coverage. Working on it now! |
...entUI.Demo.Client/Documentation/Components/PullToRefresh/Examples/PullToRefreshDefault.razor
Outdated
Show resolved
Hide resolved
...FluentUI.Demo.Client/Documentation/Components/PullToRefresh/Examples/PullToRefreshDown.razor
Outdated
Show resolved
Hide resolved
...FluentUI.Demo.Client/Documentation/Components/PullToRefresh/Examples/PullToRefreshDown.razor
Outdated
Show resolved
Hide resolved
...o/FluentUI.Demo.Client/Documentation/Components/PullToRefresh/Examples/PullToRefreshUp.razor
Outdated
Show resolved
Hide resolved
...o/FluentUI.Demo.Client/Documentation/Components/PullToRefresh/Examples/PullToRefreshUp.razor
Outdated
Show resolved
Hide resolved
|
I'm not sure why some tests are failing now, they are not tests i touched or changed i believe (An overlay test and a Listbox test). |
|
Happens sometimes. Usually running again fixes that. |
examples/Demo/FluentUI.Demo.Client/Documentation/Components/PullToRefresh/PullToRefresh.md
Show resolved
Hide resolved
examples/Demo/FluentUI.Demo.Client/Documentation/Components/PullToRefresh/PullToRefresh.md
Show resolved
Hide resolved
…5' into users/pcwvorwerk/pulltorefresh_v5
Head branch was pushed to by a user without write access
MarvinKlein1508
left a comment
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.
Tested it in Firefox.
Pull Request
📖 Description
#4185
I've tried to keep the functionality 1 on 1 as much as possible. Some things that i changed:
I was not sure if you guys wanted to try 'new' things or set up things differently in v5, but it was a nice practice for me, let me know if you wanted to start from scratch, then i will close this PR.
📑 Test Plan
Test out the component in the demo page "PullToRefresh"
✅ Checklist
General
Component-specific