Feature request: Warning messages to output the i18n path

[MechJosh0]

Warning messages to output the i18n path

Output the i18n string path in the console.warn message.

The warning message doesn't provide any information to suggest where it's originating from. You have to use the trace to find the component (or components if the string of the i18n comes from it's parents). Then if you have multiple i18ns in the component you then have to look at each one to find out which one is causing the issue.

It'd be a lot easier to debug if the warning message simply said the path of the i18n that is causing the problem.

vue-i18n/src/util.js

console.warn(`[vue-i18n] ${msg} -> "${path}"`)

Happy to make a PR if feature approved.

[exoego]

Hello @MechJosh0
Thanks for requesting new feature !!

I think there is already warning that shows keypath ${key} when message key ${key} is not found in message locale.

vue-i18n/src/index.js

Lines 270 to 274 in 6ffc601

	if (process.env.NODE_ENV !== 'production' && !this._silentTranslationWarn) {
	warn(
	`Cannot translate the value of keypath '${key}'. ` +
	'Use the value of keypath as default.'
	)

So, I think the spec of this feature need more detailed.
Do you have an idea/example of new warning message ?
That helps maintainers to understand how new message help developers!!

[MechJosh0]

Hello, You're right there is a log of the i18n key when that's not found. In my situation it was complaining it wanted a `place` name but didn't it provide the context to the error message. So it seems some error messages it'll provide the `${key}` context but not all of them.

…

On Tue, 6 Aug 2019, 11:38 am TATSUNO Yasuhiro, ***@***.***> wrote: Hello @MechJosh0 <https://github.com/MechJosh0> Thanks for requesting new feature !! I think there is already warning that shows keypath ${key} in when message key ${key} is not found in message locale. https://github.com/kazupon/vue-i18n/blob/6ffc60190d4d7910964186fd3904b77fd422a399/src/index.js#L270-L274 So, I think the *spec* of this feature need more detailed. Do you have an idea/example of new warning message ? That helps maintainers to understand how new message help developers!! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#680?email_source=notifications&email_token=ACVA4XSDKXI6K2EBTLDCAFDQDFID3A5CNFSM4IJTYYG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3UXADY#issuecomment-518615055>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACVA4XROEY6AGKPAQX6J3HTQDFID3ANCNFSM4IJTYYGQ> .