Skip warning messages when running vernacular queries

[sakekasi]

No description provided.

[HazardousPeach]

Hmm, what's the downside to just doing this filtering on the client side? What if there's a user that wants the warning messages for something?

I could potentially see splitting it into two functions, one of which handles the "common" case where you don't want to see the warnings, and the other gives you everything.

[sakekasi]

Hmm, what's the downside to just doing this filtering on the client side? What if there's a user that wants the warning messages for something?

I could potentially see splitting it into two functions, one of which handles the "common" case where you don't want to see the warnings, and the other gives you everything.

I guess it's OK to filter on the client side. In that case, we would still need to add warnings as acceptable feedback messages in self._isFeedbackMessage(). The main problem I've been dealing with is that if serapi ever sends a warning, this causes a series of cascading errors.

[sakekasi]

If you're fine with it also returning warnings, that's fine with me

[sakekasi]

@HazardousPeach , updated this PR to include warnings in the feedback messages