AuditLogActionConsts.MaxParametersLength is too short.

[Rwing]

abp/modules/audit-logging/src/Volo.Abp.AuditLogging.Domain.Shared/Volo/Abp/AuditLogging/AuditLogActionConsts.cs

Line 9 in 110f015

public const int MaxParametersLength = 2000;

abp/modules/audit-logging/src/Volo.Abp.AuditLogging.Domain/Volo/Abp/AuditLogging/AuditLogAction.cs

Line 46 in 42f37c5

Parameters = actionInfo.Parameters.Length > AuditLogActionConsts.MaxParametersLength ? "" : actionInfo.Parameters;

In some cases it's to short, should we change it to MAX ?

[maliming]

@hikalkan What do you think?

[Rwing]

@maliming Is there any workaround to this problem now? I have a system in production that needs to be solved

[maliming]

Is there any workaround to this problem now?

Unfortunately No.

[Rwing]

So sad 😢

[maliming]

You can download the audit-logging's source code and change it, then release a temporary package to solve this problem.

[Rwing]

Okay, it's a temporary solution.
But I want waitting for @hikalkan to decide how to solve this problem。

[Rwing]

Is there any plan to resovle this?

[jortygu]

just like DbTablePrefix,can cusomize MaxParametersLength

[hikalkan]

I will work on this in the next milestone to see if we can provide a simple way to make all such constants changeable.

[hikalkan]

There are two main cases;

• Making the length consts has an advantage: We can use it on data annotation properties on create/update DTOs. I know, MaxParametersLength is not something like that, but speaking in general.
• 2000+ is not working for Oracle.

However, I will try to resolve this problem with #4139
It will probably a breaking change (an easy-to-fix one, hopefully).