Steps to reproduce the issue:
Current result: The properties with the foreign key (Guid) are generated correctly with my specified name. But in the classes with postfix "...WithNavigationProperties" and "...WithNavigationPropertiesDto" the entity name is used and numbered. It would be desirable that the chosen name would be used there as well.
My expectation: In all classes where this property is used, my chosen name will be used as property name. The property name chosen for the foreign key should also be used for the navigation property (without the "Id" postfix). If necessary to define separatly with another field in the ABP Suite form.
Example: The class "Book.cs" should have two navigation properties to "Author.cs": MainAuthorId & CoAuthorId
Result in BookDto.cs, Book.cs, ...
public Guid? MainAuthorId { get; set; }
public Guid? CoAuthorId { get; set; }
Result in BookWithNavigationPropertiesDto.cs / BookWithNavigationProperties.cs:
using BookStore.Author;
using BookStore.Author;
public Author Author { get; set; }
public Author Author1 { get; set; }
The other bug is that the "using" is added twice (as seen above). I have seen this several times and would find it useful to check if the "using" is already present before adding it.
I hope my concern has been explained in an understandable way.
Thanks, Adrian
Situation: We have many entities which we want to create via ABP Suite. For each entity a folder is created. This makes the project very confusing. Therefore we have moved the entities into subfolders.
Problem: If we now make changes to existing entities, the ABP Suite does not notice that the entity already exists, because it is not in the usual folder. So the file is created again and you have to merge the changes manually, which is inconvenient. Is there a better option? Is there a way to define in which subfolders the entities are located?
Wish for the future: A possibility to group logically related entities in the ABP Suite. This can also be realized in such a way that we could define a parent folder for each entity. Such a grouping could also be included in the namespace.
ABP Framework version: v5.3.0
UI type: Blazor
DB provider: EF Core
Steps to reproduce the issue:"
The file name of the AppService class is named in singular, but the class itself is named in plural.
Example: Entity "Country":
This should match. Probably rather singular (CountryAppService).
Thanks, Adrian
I installed the preview (6.0.0-rc.3) and created a new Blazor Server App by using the template.
Because of OpenIddict, I then had to install Redis on my machine (via WSL2).
Then I did a deployment to Azure. And there I wondered why the app worked without adding the "Azure Cache for Redis".
Why does it work without the Redis service in Azure App Service? And when would it be important to use it?
By the way, in order for OpenIddict to work in Azure, I still had to do some configuration in BlazorModule. I scraped the information together from issues from others. It works, but I don't understand everything yet (e.g. generating the SigningKey & EncryptionKey) and it would be great if you could document the necessary steps to deploy it to Azure (so that the application can be run securely).
Thanks, Adrian
ABP Framework version: v6.0.0-rc.4
UI type: Blazor
DB provider: EF Core
Tiered (MVC) or Identity Server Separated (Angular): no
Steps to reproduce the issue:"
I've grouped several questions (and bugs) together here, as they all have to do with the LeptonX theme with TopMenu layout.
private void ConfigureTheme()
{
Configure<LeptonXThemeBlazorOptions>(options =>
{
options.Layout = LeptonXBlazorLayouts.TopMenu;
});
Configure<LeptonXThemeOptions>(options =>
{
options.DefaultStyle = LeptonXStyleNames.Light;
// Remove unused styles
options.Styles.Remove(LeptonXStyleNames.System);
options.Styles.Remove(LeptonXStyleNames.Dim);
options.Styles.Remove(LeptonXStyleNames.Dark);
});
}
If I remove all styles, then only the DefaultStyle appears. That would be a workaround...
options.Styles.Clear();
And it would be nice if the menu item would be automatically hidden when there is only one option.
I hope to have contributed to an even better theme :-)
Thanks, Adrian
I changed the image and had problems with the size and alignment. Now I have set the following CSS styles and so the image is set as background for this column. This way it looks great even with different screen sizes.
.lpx-login-image-area img {
display: none;
}
.lpx-login-image-area {
background-image: url("/Themes/LeptonX/Global/assets/img/login-bg.jpg");
background-position: right;
background-repeat: no-repeat;
background-size: cover;
}
I have a solution for number 4. I have implemented the boxed layout with the following CSS:
.lpx-topbar-container, .lpx-content-container {
margin: 0 auto;
max-width: 1280px;
}
8. Footer height is too big: I have discovered another new problem. The footer height is way too big (is calculated wrong). Probably the style is good for a blank / small page. But if there is content on the page, the footer becomes huge. The problem here is the min-height:
.lpx-content-container .lpx-content {
max-width: 1280px;
min-height: calc(100vh - 192px);
margin: 0 auto;
}
Hi, I have now created a new app with the latest template (Blazor Server 6.0.0-rc.4), run it and the problem occurs immediately. To illustrate it I made a screencast: AbpBug3705.mp4
Edited on 16.11.2022: Unfortunately, I can no longer reply here because the ticket is locked. But I think the problem is not solved yet and I would like to know for which version the bugfix is planned (currently I have version 6.0.1).
Thanks for the feedback about issue 2. Since these issues are probably not public, will you let me know when it is resolved?
About issue 5: I have now created a new app with Abp Suite, taking the latest template (Blazor Server 6.0.0-rc.4). Changed the layout to TopMenu and started. The problem is there from the beginning.
You can also press F5, each time the user menu will open automatically.