Hello,
We have discussed this internally. Your case is valid and our other modules follow the same rules. Pagination is wrong if we do not supply filtered data. Unfiltered data can be received without parameters anyway. So, we decided this is a bug and needs to be fixed.
I have created an internal issue for this and this will be fixed in the next release.
Thank you for your report!
This is Database Provider-specific and there is not much we can do about it.
However, you can override the IIdentityUserRepository repository which is resolved as UserRepository in the IdentityUserAppService. Then, override the GetCountAsync methods and you can write your own filtering.
Please check overriding existing repository docs for details and sample.
Please check https://support.abp.io/QA/Questions/2929/Separate-database-for-AuditLog-module-in-Application#answer-d9465c93-5195-6314-7e51-3a0351ac859d
Can you share screenshots with domain names explaining your flow step by step for us to understand better?
There is no direct support for adding Microsoft Graph to ABP and it is not in our backlog in the near future also.
However, this seems a very nice subject for a community post. Can you please make a community post request on https://community.abp.io
Thank you.
I see your point. Audit log message should also be the error message instead of type. It is a valid request and I will create an internal issue about it.
Thank you.
You are signed in to different authentication schemes so it is called multiple times. It is Microsoft Identity and you can modify as you like if you know what you are doing.
For the First login, I found that the result from ExternalLoginSignInAsync is not success. Can I add the signout there? Will it cause any problems?
If a problem occurs on based on web-server (IIS), I would suggest digging into that instead of changing the source code.
Hello,
You can create both Blazor.Wasm and Blazor.Server projects then compare the module files and configurations side by side.
I don't see any problem with your configuration. You mention you receive this error on locally also..
How can we reproduce this problem? Can you send your project or a minimal project having this issue to info@abp.com via email so that we can check?
And if I would need to execute these ef commands manually in some scenarios, this situation seriously reduces the benefit/usefulness of DbMigrator application. As you may guess reverting a migration is almost always a requirement.
No no no. reverting a migration is almost always a requirement. this is not a correct approach. Why would you alter the Migration History? What happens when some systems already have the applied version and you present a new altered migration history to update? Since you mentioned the CI/CD pipeline, why would operation delete the migration history of an application? It is not related to the application environment at all. Furthermore, how can you version your application if you keep removing migration history?
It is like it is named; migration history and it should be a part of your application life cycle. I am guessing it doesn't look or seem aesthetic (like DB table column order) so you keep removing migration history and re-creating a single one. This is against the very nature of code first application development.
So I think, it would be great if DbMigrator have some parameter <migration-name> and made the same reverting. Is there any roadmap to support such functionality?
No, because it is not DbMigrator's job description to add/remove migrations since it is directly related to Microsoft Entity Framework. Furthermore, it is used for NoSQL databases as well.