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
It seems that we don't have access to either the i18n scope or Quasar from within the mutations.js provider. Some kind of hook will be required to call the Mutator so that we can have feedback on the screen as a chromed alert, instead of just in console.log(). Although not "necessary", I prefer to translate everything from strings instead of hardwiring content into anything. This is why the API replies with a translation primitive instead of a "real response".
We have access to this stuff in common.js - so that's probably where to put it.
The text was updated successfully, but these errors were encountered:
Of course, following the "single point of authority", the translation strings could also be served by the module registry... but this doesn't solve the problem at hand.
It seems that we don't have access to either the i18n scope or Quasar from within the mutations.js provider. Some kind of hook will be required to call the Mutator so that we can have feedback on the screen as a chromed alert, instead of just in console.log(). Although not "necessary", I prefer to translate everything from strings instead of hardwiring content into anything. This is why the API replies with a translation primitive instead of a "real response".
We have access to this stuff in common.js - so that's probably where to put it.
The text was updated successfully, but these errors were encountered: