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
Some M.G.D.C.Test tests take a dependency on models in M.G service library. This is fine as long as we only need to use the non-collection models like User. Otherwise, all of the collection models and request builders take a dependency on the M.G.C which is signed.
So, we need to support tests that target M.G.C in the project, and the signed+published service library and its dependency on the signed+published M.G.C.
I think we can achieve this by adding an alias to the test reference in M.G.D.C.Test project to the M.G.C project and updating the tests to use that, and then we can add a reference to the signed+published M.G.C NuGet so we can test using the service library when it requires a reference to objects defined in M.G.C.
Another option would be to bring in the service library as a submodule, and reference it via a project via an alias.
This enables:
var deltaResponse = await deltaResponseHandler.HandleResponse<EventDeltaCollectionResponse>(hrm);
EventDeltaCollectionPage deltaResponsePage = deltaResponse.Value;
// deltaResponse.Value[0] is a property on ICollectionPage which is in the signed M.G.C
var body = deltaResponsePage.Value[0].Body; // Can't do this now
Some M.G.D.C.Test tests take a dependency on models in M.G service library. This is fine as long as we only need to use the non-collection models like
User
. Otherwise, all of the collection models and request builders take a dependency on the M.G.C which is signed.So, we need to support tests that target M.G.C in the project, and the signed+published service library and its dependency on the signed+published M.G.C.
I think we can achieve this by adding an alias to the test reference in M.G.D.C.Test project to the M.G.C project and updating the tests to use that, and then we can add a reference to the signed+published M.G.C NuGet so we can test using the service library when it requires a reference to objects defined in M.G.C.
Another option would be to bring in the service library as a submodule, and reference it via a project via an alias.
This enables:
AB#7201
The text was updated successfully, but these errors were encountered: