David Burles
David Burles
In that case you would also provide a ref on instantiation just like above. Will that not work in your case?
Hmm, can you confirm that arbitrary options make it through to `addExtension`?
I think it should be alright, you will specify the `ref` option for null collections, as well as any collections that are on a different connection. Perhaps `Mongo.Collection.getRef('...')` is better?
That will solve this outstanding issue: https://github.com/dburles/mongo-collection-instances/issues/22
Though it would be possible to overwrite a `ref` if we later define a collection with the same name which may be confusing?. The advantage of using `getRef`means the two...
Let's go with just `get`, happy for you to continue with the PR along with some tests for the new functionality
I agree, though it's not entirely working, see here: https://github.com/dburles/mongo-collection-instances/issues/22
Possibly. Let's continue discussion on the PR.
Hey @thearabbit not sure I understand exactly, could you give an example of what you're wanting to do?
Is there an incompatibility between this package and `matb33:collection-hooks` ?