Activities of "improwise"

real answer please

static async Task Main(string[] args)
{
    Log.Logger = new LoggerConfiguration()
        .MinimumLevel.Information()
        .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
        .MinimumLevel.Override("Volo.Abp", LogEventLevel.Warning)

#if DEBUG .MinimumLevel.Override("Malerifakta.CustomerPortal", LogEventLevel.Debug) #else .MinimumLevel.Override("Malerifakta.CustomerPortal", LogEventLevel.Information) #endif .Enrich.FromLogContext() .WriteTo.Async(c => c.File("Logs/logs.txt")) .WriteTo.Async(c => c.Console()) .CreateLogger();

    await CreateHostBuilder(args).RunConsoleAsync();
}

How come the logger settings is hardcoded into Program.cs and not in appsettings.json?

AFAIK, this goes against recommendations and best practices, an I fail to see a valid reason for this compared to just putting it in appsettings. This basically requires you to make code changes to modify the logging configuration, and also makes it impossible to have different configuration in different environments?

There have been a few requests about this in the past, none with an answer/resolution as it seems

https://abp.io/support/questions/1496/ABPIO-WASM---Log-level-configuration

https://github.com/abpframework/abp/issues/17333

etc.

Would imagine that there are no error logs for this as the problem is the produced code is not correct, or rather that the option to even choose this is missing.

[sumeyye.kurtulus] said: If, after the next Studio release, you still encounter blockers or regressions, we absolutely want to hear about them—preferably with concrete repro steps so we can act quickly.

As there have been at least two new releases of ABP Studio by now, is this fixed (we have not tried as we can't motivate testing every new release to see if it now works out of the box)? Thanks.

Seems like this footer is still displayed when running the API (.Host) project but only on error pages, not login pages for same URL etc.

Please do something about this service bot closing unresolved issues...

Correction, the missing data was on our end. What is not working, or rather does not seem possible to select in ABP Suite, is if Navigation properties should be listed in the List view like for normal properties. Please not that the Filterable option does not seem to affect this, ie it will happen even if you deselect that.

Hi,

It seems like ABP Suite has some problems generating CRUD pages for Angular when there is navigation properties.

First, there seem to be no way not to get Navigation properties added to the list view (besides manually removing them afterwards of course). Second, it also seems like the code generated to actually fetch those navigation properties to show isn't working either. So you will end up with unwanted empty columns. If you open the row in Edit mode, everything seem to work fine, including the dropdowns for District and Employer and populated with correct lookup data.

[maliming] said: The LeptonX Lite LeptonX link seems no problem.

That specific problem is for the MVC version.