luxoft / bssframework Goto Github PK

Move custom reports to different repository

Remove old Silverlight code generators
Remove generated code

added IRuntimePermissionOptimizationService

Run integration tests using GitHub Actions

Model methods

Please remove Workflow with all dependencies COMPLITELY!

This is legacy code and doesn't use anywhere

subj

When generating xsd schemas, we need the 'schemaLocation' attribute to be present in 'import' tag with a relative path to the correct file.

Example: by default, it is now generated like this: <xs:import namespace="http://microsoft.com/wsdl/types/" />

correctly it should be like this: <xs:import schemaLocation="./microsoft_com_wsdl_types__1.xsd" namespace= "http://microsoft.com/wsdl/types/" />

We must have opportunity to call native NHiberante Async methods

Update NHibernate to 5.3.11

Now we use Hangfire

I want to do it something like this

public class Test
{
   public Test(IDefaultBllFactory bllFactory)
   {
      this.bll = bllFactory.Create<Employee>();
   }
}

Remove legacy DBSubsctiption from codebase

By default Isolate level Read Committed

I want to get some services from DI in mapping settings

DependencyInjectionExtensions.AddDatabaseSettings

The CAP has issue with TransactionScope (dotnetcore/CAP#1076)

Current fetch syntax vary abstract f => f.Select(z => z.Initiator).Select(z => z.Owner)
Please add support NHib syntax f => f.Fetch(z => z.Initiator).Fetch(z => z.Owner)

• Workflow
• AttachmentContainer
• UserActions
• DBSubscription
• RegularJobs
• ???

Use the latest version of .NET

subj

Throw exception

Unable to resolve service for type 'Framework.SecuritySystem.IDomainSecurityService`2[Currency, SecurityOperationCode]' while at
tempting to activate 'DAL.RepositoryFactory`1[Currency]'.

Fix CAP controller

Compare https://dynamic-linq.net/ and https://github.com/Luxoft/BSSFramework/tree/main/src/Framework.ExpressionParsers
If dynamic-linq has same functional please remove ExpressionParsers

• CustomReports
• ByRow

Use unsupported EPPlus

Some methods contains more than one parameters that ASP.NET Core not recognize

Add specification support to repository

IParentSource.Parent must be nullable

Prepare release and publish to nuget

Create own nuget package for AttachmentContainer.
With the ability to connect to the new framework version

Rename
Func<S, TKey> getSKey, Func<T, TKey> getTKey
for better understanding

Describe the bug
For example, we have class that has value object type property

public class DomainClass1 : AuditPersistentDomainObjectBase 
{
    public virtual Component? Component { get; set; }
}

// where Component is 
public class Component : ValueObject
{
    public virtual DomainClass2? DomainClass2 { get; protected set; }
}

And fetch for this classes structure doesn't work, inspite on Nnhibernate Support.

...
bll.GetUnsecureQueryable(f => f.SelectNested(x => x.Component ).Select(x => x!.DomainClass2)).ToList();
...

As result low performance and big amount of useless requests.

To Reproduce
For reproducing use same classes structure as described above

Expected behavior
Fetch must work, amount of requests to database must decrease

If you change the name of the principal in the configurator to a name that already exists, the system will give an error, but save the changes.

The current syntax with the Evaluate doesn't fit into the new DI and Async paradigm.
We need new concept.

Try to use WorkflowCore for Authorization