You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically there is an analyser package that helps with LINQ query building. It likely looks for certain interfaces that exist in the official driver but there may still be ways to get it to work.
If it doesn't work out-of-the-box, it might be worth seeing if a PR to the library (assuming it is open source) can add a more generic support to it making queries easier from MongoFramework consumers.
Tasks:
Does it work out of the box? If so, nothing to do!
If it doesn't, look at the source of the analyser to check what it is looking for.
If it is looking for an interface with the official driver, plans would need to be created to work out how to do it generically - even if it is a little cumbersome on our side of things.
If it is looking for some other pattern, that needs to be discussed to work out the best course of action (we might be able to change our side of things to make it work).
If possible, it would be great if it could be an attribute or something - especially if the lookup is by the attribute name directly. That way we don't need to reference the same library.
I mean, maybe if it is by interface name, we might be able to have an internal interface that the analyser might still pick up.
The text was updated successfully, but these errors were encountered:
See: https://www.mongodb.com/developer/article/introducing-mongodb-analyzer-dotnet/
Basically there is an analyser package that helps with LINQ query building. It likely looks for certain interfaces that exist in the official driver but there may still be ways to get it to work.
If it doesn't work out-of-the-box, it might be worth seeing if a PR to the library (assuming it is open source) can add a more generic support to it making queries easier from MongoFramework consumers.
Tasks:
If possible, it would be great if it could be an attribute or something - especially if the lookup is by the attribute name directly. That way we don't need to reference the same library.
I mean, maybe if it is by interface name, we might be able to have an internal interface that the analyser might still pick up.
The text was updated successfully, but these errors were encountered: