Ability to pass indexes in aggregate repo?

[lucagiove]

It's true that it is not a best practice but it often happened to need it (email, legacyIds, other ids), I would prefer to keep all the repo as much coherent as possible, so I would add this also to the aggregate repo.
What do you think @gtoselli ?

[gtoselli]

You can always do it by accessing the collection outside the repo and running an ensureIndexes. Is it necessary to bring it inside?

[lucagiove]

Of course you can, but a field would encapsulate more the db logic.
And doing manually requires to override the init method that add more complexity.

It happened that some dev, to override this missing functionality, have specified indexes in query repo instead of aggregate repo because in that specific case they were the same collection..

I think indexes are more properties of a repo than an action to be performed.