Starts in:
2 DAYS
3 HRS
37 MIN
43 SEC
Starts in:
2 D
3 H
37 M
43 S

Activities of "burkay"

Hello Shiwei,

Thank you for your response.

Best, Burkay

Hello Shiwei,

I got an email saying this is closed by ServiceBot. You mentioned that you would be reaching out to the team for input, and I was wondering if there have been any updates or developments regarding it.

Thank you for your help, and I look forward to hearing back from you!

Best, Burkay

I created a new project with ABP CLI 8.3.3 as you suggested earlier. The problem is fixed. Thank you for the fix and for the refund :)

Thank you! I wlll check it as soon as possible. Meanwhile, since this required a fix on your part, could you refund our question credit?

Thank you!

Please note that if that is the case, the second rule is completely useless and unnecessarily increases the bundle size. I want to believe that it is there for a reason. We already have a workaround and just wanted to bring this to your attention. Could you also tell your teammate about this? Thank you.

Awesome, thank you!

Hello,

I updated the ABP CLI to the version 7.2.2 and created a new project with the below commands:

dotnet tool update -g Volo.Abp.Cli
abp new Acme.BookStore -u angular -dbms PostgreSQL -csf

Then followed the steps in the original post with only two tabs. Sent the log file to your e-mail. Please note that there are JavaScript errors as well. Screenshots below.

Answer

Thank you!

Answer

Hello,

We are fine with this mapping. The problem is the change about how angular ui handles the exception. Let me explain it in detail.

I created a new project with the latest ABP Suite. Added a simple service method with the below code

        public async Task<PagedResultDto<LanguageDto>> GetListAsync(string exceptionType)
        {
            var list = await _languageRepository.GetListAsync();

            switch(exceptionType)
            {
                case "businessException":
                    throw new BusinessException("BE", "Business exception");
                case "userFriendlyException":
                    throw new UserFriendlyException("UFE", "User friendly exception");
                case "abpValidationException":
                    throw new AbpValidationException("AbpValidationException");
            }

            return new PagedResultDto<LanguageDto>(10, ObjectMapper.Map<List<Language>, List<LanguageDto>>(list));
        }

Then added three buttons to the home page to call this method with different inputs.

First, in packages.json, I set versions of all the abp related packages to 7.1.1. Clicked on the three buttons. All the response status codes are aligned with your messsage. They all show the responses in a dialog without leaving the current page. Screenshots are below.

7.1.1 Business Exception

7.1.1 User Friendly Exception

7.1.1 Abp Validation Exception

Then, in packages.json, I set versions of all the abp related packages to 7.2.1. Repeated the same procedure. Got the same responses with same response status codes. However, in BusinessException and UserFriendlyException cases, the current page is left and the eror page is shown. After clicking on Go back link, original page is opened with the error dialog. Our problem is this change of behavior in angular side of exception handling. Screenshots are below.

7.2.1 Business Exception

after clicking Go back

7.2.1 User Friendly Exception

after clicking Go back

7.2.1 Abp Validation Exception

We want to keep using BusinessException and UserFriendlyException without this behavioral change. I hope I can clarify the issue better now.

Best wishes.

Showing 1 to 10 of 16 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06