We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As per this thread: MarimerLLC/cslaforum#938
The RefreshAsync method is very opinionated and may not offer enough value to overcome the confusion is creates.
RefreshAsync
Or perhaps it should accept an expression so the data portal can be invoked directly:
vm.RefreshAsync(async () => await DataPortal.FetchAsync<DomainType>());
The text was updated successfully, but these errors were encountered:
MarimerLLC#1585 Add overload for RefreshAsync to accept data portal m…
9ee3667
…ethod
MarimerLLC#1585 Eliminate RefreshAsync that accepts param array
1e07f18
The final implementation here is to remove the old RefreshAsync method in favor of a new one that accepts a data portal or factory method:
await vm.RefreshAsync(() => DataPortal.FetchAsync<PersonEdit>(123));
Sorry, something went wrong.
MarimerLLC#1585 Add GetKey extension method
f454842
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
rockfordlhotka
Successfully merging a pull request may close this issue.
As per this thread: MarimerLLC/cslaforum#938
The
RefreshAsync
method is very opinionated and may not offer enough value to overcome the confusion is creates.Or perhaps it should accept an expression so the data portal can be invoked directly:
The text was updated successfully, but these errors were encountered: