Closed ArtManyak closed 10 months ago
Thanks for the info, the plugin will need an update indeed.
Please tell if you need help with the update.
Thanks for offering help 🙂
The fix was easy, and I just submitted an update.
Actually I'll have a question @ForNeVeR 😅
I got the following verification result:
It says compatible, but does the defect block the update? And can/should I just change the plugin id? Can I use the same id as for the ReSharper plugin?
@ltrzesniewski, for now this is a mere warning, and I am not aware of any plans to block further updates of plugins with "invalid" plugin ids. And changing of plugin id is tricky.
This validation was put in place relatively recently (definitely later than you published a plugin for the first time).
I'll open an internal discussion on this topic, thanks for notifying me. Abc.MoqComplete is not the only plugin that triggers this validation issue.
Ok, I'll leave it as-is then. Thanks for the info! 🙂
I bring the answers: it is planned to disable the plugin id validation for the existing plugins. So, this won't be a problem for too long. Just ignore it for now.
Makes sense. Thanks!
Rider and R# contains breaking API change. Which produces a lot of exceptions when MoqComplete is installed.