Closed lyrixx closed 1 year ago
How can we move forward with this idea?
From what I see, we miss some documentation?
I need some time...
And we need to take a decission: Do we support only one connection, or do we allow many?
IMO, we should go simple as first implementation and support only one connection, if someone has needs for more we can create a new issue and make a new iteration of that feature later.
I would like to avoid that.
Because supporting theses two configuration is really boring
client:
host: 127.0.0.1
mapping: data/mapping.yaml
client:
default:
host: 127.0.0.1
mapping: data/mapping.yaml
another:
host: 127.0.0.2
mapping: data/mapping2.yaml
I already have a POC on my computer to support N connexion. I need not so much time to finish it I guess
I agree with @lyrixx, multiple connexion from the start is good. We must solve the autowiring that's all.
I just pushed a new version. still in WIP
The configuration has the following shape:
elastically:
connections:
default:
prefix: null
index_class_mapping:
my-index: My\Dto
serializer:
context_mapping:
foo: bar
client: []
mapping_directory: ~
Here we go! New version published. I added everything I wanted. I wrote some documentation. Can I have a review please? And if it's okay, I'll write some tests eventually
Thanks!
See the readme for more information