@alper I have been a customer for years, and I'm sure if anything, I'm cooperating with the framework by sharing my challenge here. There are multiple ways of getting around that, and bringing this to attention is the right call. If you have read my message and the response I provided, you would see nothing but cooperation.
@mailiming Thanks for the acknowledgement and for having a closer look at the problem I described. That fix should resolve the issue for me and any other ABP users looking to do that in the future. Much appreciated!
This makes me feel that you either didn't understand what I said or that you don't want to try by yourself. For most of your customers, we have real IP in our projects, and a lot of them would be large enough not to be shared here.It's a job in itself to create a new project just to share it here.
public async Task<IActionResult> GetSomethingByDateAsync([FromQuery] DateOnly? date)
{
yourAppService.GetSomethingByDateAsync(date); // Before it reaches the AppService the ABP Validations will throw an exception when date is null despite being a nullable DateOnly
}
If you look at your code, there's no App Service dependency accepting the DateOnly. Instead of having a Redirect create an AppService that accepts DateOnly? and you will see what I described above.
I provided an example on my request, but if you have any API projects on ABP, as I assume you do, please do the following:
public async Task<IActionResult> GetSomethingByDateAsync([FromQuery] DateOnly? date)
{
yourAppService.GetSomethingByDateAsync(date); // Before it reaches the AppService the ABP Validations will throw an exception when date is null despite being a nullable DateOnly
}
There's no [Required] attribute or custom logic enforcing it.
I have started from scratch, trying to perform the same actions that our runners would do, and I didn't have any major slowness. I will follow up with GitHub to see what might be going wrong. If anything requires adjusting ptIf any further actions are required, I will reopen this ticket..
My case is exactly the same as the above but I instead of changing only AllowChangingEmailSettings I wanted to ensure that the group name was consistent with new features being added. In that case, I'm trying to create a structure similar to namespaces (i.e. GroupName + "Products.MyProductName instead of only GroupName + "MyProductName
Any thoughts?
We need the swagger files in there as we are overriding the default ABP behaviour for authentication. Thanks for sharing how to disable it.
My app is very basic. As you can tell, I use Swashbuckle, which is provided by ABP. As you can from my other posts, I'm not starting on ABP now. I'm migrating from v8 to v9.
If you are able to open one of your v8 API projects (i.e. no UI) where you don't have a package.json and if you upgrade that to v9, you will be able to reproduce that.
Please note that I had to manually copy the libs folder indicated below as I don't have package.json as part of my project.
I'm not sure if you followed what I said. Did you run an API project with Swagger? You have to keep serving the /swagger/index.html which goes under wwwroot.
If you did follow what I said, could you please show me how I run Swagger without wwwroot?
Given this is not a part of the migration guide present here: https://abp.io/docs/9.0/release-info/migration-guides/abp-9-0 could you please update the info so other people don't get lost with the same issue?
Also, I don't know how the ticket system works, but for things like this and the other ticket I opened, I think the most reasonable way forward would be to not reduce the number of tickets we have as part of our agreement with Volosoft
