simplifynet / simplify Goto Github PK

Is your feature request related to a problem? Please describe.

1. ObservableCollection does not contain AddRange method, but has Add method.
2. It also does not raise an event on item change, just only on item addition/removal.

Describe the solution you'd like

1. Add extension method AddRange
2. Add extension method RefreshItems

Describe alternatives you've considered

Additional context

Once fixed: https://nhibernate.jira.com/browse/NH-465

• All methods should be wrapped to explicit transactions
• Add check that if transaction is open then BeginTransaction and Commit should be skipped
• IsolationLevel should be set in constructor

Is your feature request related to a problem? Please describe.
Could not inherit record type from class.

Describe the solution you'd like
For example, inherit CustomRecord from IdentityRecord.

Describe alternatives you've considered
Just a new record type, delivered with C# 9.0.

Additional context

Is your feature request related to a problem? Please describe.
Simplify.Extensions features extends the System namespace. So that extensions can be moved to the Simplify.System project.

Describe the solution you'd like
Move extensions to the Simplify.System.Extensions namepsace in the Simplify.System project.
Delete the project Simplify.Extensions.

Is your feature request related to a problem? Please describe.
AutoMapper is a great mapping/validation tool. It delivers conventional mapping that provides mappings with just one line of code.
But there are some usecases when we need to write complex mappings with ton of properties using ForMember method. As a result there are large source files with low readability.

Describe the solution you'd like
To write simple mapping rule for some property, we use following code: ForMember(dest => dest.X, opt => { opt.MapFrom(src => src.X); ... })
Alternatively, we can write something like:
Map(dest => dest.X, src => src.X, opt => ...) with options enabled,
or Map(dest => dest.X, src => src.X) when there is no need for custom options,
or Map(dest => dest.X) when destination member is mapped directly from source object.

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.

1. Using system derived namespace System.Xml.XPath, we can get elements by methods XPathSelectElement and XPathSelectElements.
   It is hard to read the code with tons of that methods, for example when parsing large Xml document.
2. We cannot use local variables that store temporary XElement objects, in expressions, for example in AutoMapper mapping expression.
   Need to define Func<XElement,XElement> to use it in expressions.

Describe the solution you'd like

1. Add shortcut extension methods for XElement methods:

• "Get" for XPathSelectElement
• "GetList" for XPathSelectElements

2. Add extension method that will return Func<XElement, XElement>.

Is your feature request related to a problem? Please describe.
Simple singleton can be implemented via private property _instance and a public one named Instance. Once created, it holds reference to the targeted object over application lifetime until termination.
WeakReference can be used in cases when there is no need to hold object reference over long time. Its target can be deleted with garbage collector in short period of time. Correct implementation of Singleton over WeakReference is not hard but repeatitive.

Describe the solution you'd like
Implement WeakSingleton that holds singleton logic over WeakReference.

Describe alternatives you've considered
Dependency injection is a great alternative and a preferred one. But in cases where there is no DI in some projects and importing DI features to those projects is painful or just overhead, it is useful to have that sort of custom singleton implementation,

Specification:

public OffsetStopwatch(TimeSpan startOffset = default)
{
	StartOffset = startOffset;
}

public TimeSpan StartOffset { get; }

public TimeSpan Elapsed => throw new NotImplementedException();
public long ElapsedMilliseconds => throw new NotImplementedException();
public long ElapsedTicks => throw new NotImplementedException();

public new static OffsetStopwatch StartNew()
{
	throw new NotImplementedException();
}

Is your feature request related to a problem? Please describe.

Current schema update script looks like this

[Test]
public void UpdateSchema()
{
	var configuration = new MySessionFactoryBuilder(/* IConfiguration */)).CreateConfiguration();

	Configuration config = null;
	configuration.ExposeConfiguration(c => config = c);
	configuration.BuildSessionFactory();

	config.CreateIndexesForForeignKeys();

	var updater = new NHibernate.Tool.hbm2ddl.SchemaUpdate(config);
	updater.Execute(true, true);
}

Describe the solution you'd like
This code can be moved to Simplify.FluentNHibernate as an extension method for FluentConfiguration with ability to extend Configuration

Is your feature request related to a problem? Please describe.
ObservableCollection does not work properly in concurrent mode. It raises events on items addition/removal, that are not handled by watchers, if collection is changed asynchronously / on another thread.

Describe the solution you'd like
Add class ConcurrentObservableCollection, that inherits ObservableCollection and adds concurrency feature.

Describe alternatives you've considered

Additional context

Before

DIContainer.Current.Register<IBar, Bar>();
DIContainer.Current.Register<IFoo, Foo>();
DIContainer.Current.Register<IBar>(p => new Bar2("test"));

After

DIContainer.Current.Register<IBar, Bar>()
    .Register<IFoo, Foo>()
    .Register<IBar>(p => new Bar2("test"));

https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-1/

MultitaskScheduler does not set AppName as SingleTaskScheduler