Activities of "rafael.gonzales"

Just one thing to add, it's that those tests I had a response time of 6 seconds when I had many localization pending to be added in the en.json file. After those localization were added the response time changed a lot.

It's not perfect but it gets better

This might not be the good reference you are looking for but right now I'm in the middle of a custom menu provider for ABP and I experienced some issues with ABP + Redis

Using a multi-level menu environment with Redis, I have experienced a waiting time of almost 6 seconds

I disabled the distributed locking and removed any reference for Redis in my ABP project and ran the same application and now it runs in milliseconds

I couldn't take the screenshot before but It takes 2 seconds per key for ABP to get Permissions and Settings from Redis Cache. while in memory it only takes milliseconds.

While in Redis, ABP takes too much to retrieve information from the PermissionStore cache in Redis. It seems that if you have a more complex menu or multi-level menu or much more information related, It gets complicated for ABP to get from Redis.

If you look at the end of the following picture, you get high consumption in a single row from Redis.

There is a bug in LeptonX

In Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX\Themes\LeptonX\Components\SideMenu\MainMenu\Default.cshtml

LeptonX is not adding the custom ID that you can set when you create a Group in the ApplicationMenu

@foreach (var group in Model.Menu.Groups)
{
	var menuItems = Model.Items.Where(x=> x.MenuItem.GroupName == group.Name).ToList();
	if (menuItems.Any())
	{
	//HERE IT'S MISSING THE ELEMENT ID YOU CAN SET WHEN YOU CREATE A GROUP IN THE MENU
		<li class="group-menu-item hidden-in-hover-trigger">
			@group.Name
		</li>

		@foreach (var menuItem in menuItems)
		{
			menuItem.IsInRoot = true;

			<li class="outer-menu-item">
				@await Html.PartialAsync("~/Themes/LeptonX/Components/SideMenu/MainMenu/_MenuItem.cshtml", menuItem)
			</li>
		}
	}
}

I am in the same position as you. Running without redis is much faster. I guess because It requires a standalone reddis to work propperly but I am still investigating too

I'm having this constant issue in 8.0.2 and It won't create validations for that property

The new version of ABP Suite 8.0.2 is not adding integer or float validations for properties, It's not adding the [Range] attribute

I would like to see it in the ABP Suite.

• Nullable strings option
• Decimal range and precision
• DateRange option in ABP Suite
• Add Spanish (Mexico) and Spanish (Peru) in the localization (In Spanish, we have different decimal validations between Spain (es) and South America (es-MX or es-PE)
• Ability to add nested details

There is no DataSeedContributor for Detail Entities.

This issue has not been resolved https://commercial.abp.io/releases/pr/16413

It's still happening the issue with the test and the one-to-many relationship. You need to validate the one-to-many when it's related with a Detail in the Master/Detail functionality.

Steps to reproduce.

Create a Master Entity named "RelatedDemo" Create a Master Entity named "MasterDemo" Create a Detail for "Demo" and name it "DemoDetail"

In the "DemoDetail" configuration, add a one-to-many with "RelatedDemo"

• Generate "RelatedDemo"
• Generate "MasterDemo"
• Generate "DemoDetail"
• Re-generate "MasterDemo" (You need to re-generate the "MasterDemo", because if you don't do this, it will generate an issue because the DtoGenerated in "MasterDemo" after you create the detail it's of type "WithNavigationProperties" instead of the Dto one so you need to re-generate the "MasterDemo" so it will include in the automapper an Ignore for that property.

It will throw a similar error but instead of looking for the full namespace for the RelatedDemoDataSeedContributor. It will start to look for the file in the Master entity folder instead of the folder "RelatedDemo"

Could not find file 'C:\Users\User\Documents\GitHub\demo802\modules\DemoModule\test\DemoModule.Domain.Tests\MasterDemo\RelatedDemoDataSeedContributor.cs'.

UPDATES

It also happens when you have TWO one-to-many relationships of the same entity. It tries to look the DataSeedContributor of the related entities from the destination entity folder

in the CLI, abp update it's not updating the project to the latest version 8.0.2. Either it's applying any changes to the code related to the new version.