This sort-of depends on this pull request that will cause Virtus to call our initializer. Until that time, I've added a monkey patch that fixes the behaviour for the current release. This patch is locked to the specific version that needs it.
Coverage decreased (-0%) when pulling efb3dabb7f85536a137d3119d259a0922f8fa12f on feature/virtus into 4df36e28ca880d826e5333bcf01beff990136940 on feature/new-api-proposal.
Coverage decreased (-0%) when pulling efb3dabb7f85536a137d3119d259a0922f8fa12f on feature/virtus into 4df36e28ca880d826e5333bcf01beff990136940 on feature/new-api-proposal.
Coverage remained the same when pulling bc606052159f606566fbdb2ffd521964200397a7 on feature/virtus into 1d8092b0eacc55e729eb04fd327ba8dda326a33f on feature/new-api-proposal.
This sort-of depends on this pull request that will cause Virtus to call our initializer. Until that time, I've added a monkey patch that fixes the behaviour for the current release. This patch is locked to the specific version that needs it.