Hi,
Are you talking about this? https://docs.abp.io/api-docs/abp/3.0/api/index.html
Yes, something like this but with documentation for the methods and classes instead of a simple listing. I also see this is version 3. Are there plans to release documentation for higher versions?
His name is Vineet Belani. We asked about this and he said he would look into it because he was sure he'd seen it before. After a while, he responded that it was no longer available and we should make a request for it through the support forum here.
Has there been any progress since those issues reported by the AI above? Or are we stuck with dealing with the warnings?
I'm not sure the AI answer makes sense.
I have already overriden the layout file and replaced the @Body with the <Div Class="layout"><RouterTabs /></div> as described in the Blazorise documentation.
The RouterTabs component captures the navigation of the pages and renders the page components into tabs.
The problem is that the Toolbar is not part of the Body of each page, and thus it is not rendered inside the tab.
Also, RouterTabs get the type of each page and place its name in the tab name.
The <div/> does not have any significance. The body of any page is rendered inside the <RouterTabs/> component. Unfortunately, <RouterTabs/> does not support layout sections inside it. It just renders the page's body.
Rewriting the LeptonX source code or providing a custom layout would not help as the ABP pages expect any layout used to contain a Toolbar section. I could rewrite all the ABP pages to place their toolbar inside their body, but I would like to avoid that.
Besides that, the RouterTabs component expects an attribute in each page to provide the name of the page. The ABP pages do not have this attribute and thus the RouterTabs component uses their type name as the name.
Do you have an alternate suggestion to RouterTabs or a workaround to the above problems?
The AI basically reiterated what I said. I don't have a _Host.cshtml in a Blazor Web App project and the .AddBlazorise is already done by Volo.Abp.BlazoriseUI. AddBootstrapProviders() and AddFontAwesomeIcons() are not done, but wouldn't they be done if BlazoriseUI needed them?
Please answer again to my original questions.
I sent a project. You can switch between the commented lines for different results of the test. Without the BlazorStandardBundles, calling IBlockUiService and IUiNotificationService produces exceptions. With the BlazorStandardBundles, IBlockUiService works correctly, but IUiNotificationService does nothing.
private void ConfigureBundles()
{
//Create the global bundle
Configure<AbpBundlingOptions>(options =>
{
options.StyleBundles
.Add("MyGlobalBundle");
//options.StyleBundles
// .Add("MyGlobalBundle", config =>
// {
// config.AddBaseBundles(BlazorStandardBundles.Styles.Global);
// });
options.ScriptBundles
.Add("MyGlobalBundle");
//options.ScriptBundles
// .Add("MyGlobalBundle", config =>
// {
// config.AddBaseBundles(BlazorStandardBundles.Scripts.Global);
// });
});
}
Are you saying that it is necessary to have a theme for a minimal ABP application to work? I thought ABP was meant to be modular in the sense that you only installed what you needed and the installed modules did the setup for whatever dependency they needed.
Also, the services that I mentioned were not working (the block service and the notification service) are just those I've noticed. Is there another service from the initial packages (and their dependencies) that might not work even if I use a theme?
Thank you very much for the layout. I see now that some services need hooks in the layout to work. I would suggest a note in the documentation of those services mentioning the necessary setup in case a theme is not used or is being customized.