public void RemoveEmptyStrings()
{
// Look for changes
this.ChangeTracker.DetectChanges();
// Loop through each entity
foreach (var entity in this.ChangeTracker.Entries())
{
// Use reflection to find editable string properties
var properties = from p in entity.Entity.GetType().GetProperties()
where p.PropertyType == typeof(string)
&& p.CanRead
&& p.CanWrite
select p;
// Loop through each property and replace empty strings with null
foreach (var property in properties)
{
if (string.IsNullOrWhiteSpace(property.GetValue(entity.Entity, null) as string))
property.SetValue(entity.Entity, null, null);
}
}
}
This issiue important for us, is there any news
Is It possible to check this request again? https://github.com/abpframework/abp/issues/7231
Hello, We cannot find any UI page about Background Jobs in commercial (angular) web panel. Is there your a roadmap planning about Background Jobs Management UI page(s)
Hi @gvnuysal,
It isn't related with your license, it's related to ABP version. You should upgrade to latest stable version.
Create new CRUD by CRUD Generator
ABP Framework version: v4.3.0 UI type: Angular DB provider: EF Core **Tiered (MVC) or Identity Server Separated (Angular): **no
When I create a new CRUD entity I get this error:
[11:40:08 INF] Running the Angular Schematics command: npx "C:/Workspace/OrderManagementSystem/src/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro Neuca.OrderManagementSystem "C:/Workspace/OrderManagementSystem/src/aspnet-core/.suite/entities/Sample.json" [11:40:18 INF] Angular Schematics command failed. npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:/Workspace/OrderManagementSystem/src/angular/.suite/schematics/node_modules/.bin/ng/package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Workspace\OrderManagementSystem\src\angular.suite\schematics\node_modules.bin\ng\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
Hi @tomasz.lewandowski,
We had same problem and solved via below method :
Can you check npm and node version ,
npm -v
node -v
node version should be 14 and npm version should be 6.*
see also:
https://support.abp.io/QA/Questions/807/Bugs--Issues-v42X#answer-a3396338-ee7a-4f99-4f78-39fae1635298
@armanozak It would be nice if Abp suite did the version check (npm and node)