Looks good to me in general.
But we should add IDependencyResolver {get;set} to IgniteConfiguration
class instead of changing IIgnite interface.
We need the resolver at startup before IIgnite instance is created, to
resolve user-defined cache stores and so on.
And we should make sure to add tests
Hello,
I propose the following.
*Development*
1. Define *IDependencyResolver* in *Apache.Ignite.Core* under
*DependencyInjection* folder that contains at least 2 methods:
*T Resolve(object arguments = null);*
*object Resolve(Type type, object arguments = null);*
2. Create *InjectResolvableAttr
Hi Artyom,
Ticket already exists: https://issues.apache.org/jira/browse/IGNITE-9299
Feel free to grab it.
But before diving deep into coding, can you please provide a short overview
of the proposed implementation?
Either on dev list or in JIRA ticket directly.
Thanks,
Pavel
On Mon, Sep 10, 2018
Hello Artyom,
Welcome to the Apache Ignite community! I've added you to the list of
contributors, you should now be able to assign tickets to yourself.
Get familiar with Apache Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
Instr
