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
There are a number of matcher objects in Magespec that do not appear to be used anywhere.
The following matchers are currently defined:
BeInArea
BeOfType
Contain
DispatchEvent
HaveHeader
HaveName
HaveStatus
MatcherCollection
RenderLayoutHandle
RenderTemplate
RespondWith
Translate
Of these, only BeInArea has any contents. It appears to be trying to use an underlying Mage object to determine which site area a controller exists in. Since we do not currently support an underlying Mage object, this seems like it requires a decision on how integrated Magespec should be.
For all the empty matchers, we need to decide whether they should be implemented or not. Some of them will not be at all practical in a non-integrated tool.
The text was updated successfully, but these errors were encountered:
There are a number of matcher objects in Magespec that do not appear to be used anywhere.
The following matchers are currently defined:
Of these, only BeInArea has any contents. It appears to be trying to use an underlying Mage object to determine which site area a controller exists in. Since we do not currently support an underlying Mage object, this seems like it requires a decision on how integrated Magespec should be.
For all the empty matchers, we need to decide whether they should be implemented or not. Some of them will not be at all practical in a non-integrated tool.
The text was updated successfully, but these errors were encountered: