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
In the readme, this package states that other plugins have to be added after this one, in order to have their property assertions be converted to methods BUT chai-as-promise have to be added first. Now the chai-as-promise package state that other plugins have to added BEFORE itself in order to use them with .eventually. This means that we have to choose if we want other plugins be usable with as-promise or convert their properties to methods. I would want to do both.
I tried adding dirty-chai as the last plugin, and it still works, so has the above been changed and the readme not updated? Or am I missing something?
The text was updated successfully, but these errors were encountered:
Yeah, this is a bit confusing. Some changes have been made to the library in order to relax the inclusion order sensitivity, and the readme was never updated accordingly. I'll see if I can put some work into testing with some other popular plugins and update the documentation to be more accurate as to any hard ordering requirements.
In the readme, this package states that other plugins have to be added after this one, in order to have their property assertions be converted to methods BUT chai-as-promise have to be added first. Now the chai-as-promise package state that other plugins have to added BEFORE itself in order to use them with .eventually. This means that we have to choose if we want other plugins be usable with as-promise or convert their properties to methods. I would want to do both.
I tried adding dirty-chai as the last plugin, and it still works, so has the above been changed and the readme not updated? Or am I missing something?
The text was updated successfully, but these errors were encountered: