v0.3.0 Potentially errant console.error statement in filterInvalidTokens #300
Description
Between versions v0.2.14 and v0.3.0 there was a console.error statement committed to the filterInvalidTokens action. This logs out regardless of whether or not invalid token are found.
Looks like it was added in this PR: #291
Was this additional logging intentional, or can it possibly be removed? If it's intentional and the desire is to keep this sort of logging around, would it be possible to only log out in the event that invalid tokens are found for a given path?