wangsizhu0504 commented on issue #3520: URL: https://github.com/apache/incubator-streampark/issues/3520#issuecomment-1914027036
> That sounds like a reasonable approach, but I believe it would be better to have all the i18n localization files placed on the frontend. This way, the frontend can handle all the translations internally and keep the display logic separate from the backend services. It also simplifies the backend since it only needs to provide error codes, and we won't need to maintain a separate i18n querying API. Let me know your thoughts on this. Kriszu ***@***.***> 于2024年1月29日周一 11:42写道： > […](#) > @wangsizhu0504 <https://github.com/wangsizhu0504> @RocMarshal <https://github.com/RocMarshal> ，Can you help me finish this? ok, cool, We can provide an api interface to query i18n, and the other interfaces will return errorCode instead of the original error message.what do you think — Reply to this email directly, view it on GitHub <[#3520 (comment)](https://github.com/apache/incubator-streampark/issues/3520#issuecomment-1913909771)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMSNTBGGWGQT77PHTA6EFEDYQ4LDLAVCNFSM6AAAAABCOXCTH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTHEYDSNZXGE> . You are receiving this because you were assigned.Message ID: ***@***.***> You can put the internationalization identifier chosen by the front-end user into the header of the api interface, and the back-end will parse the internationalization field in the header and return an error message dynamically. ```ts headers:{ language: ‘zh_cn’ } ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
