Issues upgrading from v4.12.1 to v4.13.0 #4269
Unanswered
sanderkemna
asked this question in
Q&A
Replies: 2 comments
-
|
So your second issue is solved, right? For the first one, I suggest you create an issue (with ready-to-run reproduction code) so we can take a look at what is happening. One thing you can try before that is to use the ps as a Dutchie, I love your username :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes, the second issue is solved, I guess it was more meant as a suggestion to add a notion in the patch notes or breaking changes about it. I'll try your suggestion for the first one, and post an issue if needed. Thank you for your time! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I would just like to give a huge thank you for creating & maintaining this package, its been off tremendous help to me!
After upgrading from 12.1 to 13.0 I noticed two issues and I couldnt see it mentioned in the docs so figured to post it here:
Dialog window not showing up anymore.
I have a regular method that opens a dialog whenever a save is done. After the upgrade it compiles and I can debug through the code, but it wont popup the dialog:
FluentAutoComplete has no option to call context.Any() anymore, but instead you can call context.Items.Any().
A regular AutoComplete is calling the context to adjust the FooterContent accordingly. It was working before but after the upgrade it gave some really weird compiling errors (which I guess Blazor does more often), so it took a while before I figured this out.
Beta Was this translation helpful? Give feedback.
All reactions