-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device name, profile name, resource name, and command name supports Chinese naming #4053
Comments
This issue is closely related to this one #3935 . At the May 2022 planning meeting, we discussed this need. We left it in the backlog but decided not to address this in this release (Levski). Reconsider in future planning meetings given multiple needs now. |
Maybe we can just allow |
Maybe our validator needs to be reversed to not allow specific characters (space, comma, etc.) rather than restrict to limited set of characters. This should allow Chinese characters?? |
yes, we can discuss in the next Core WG meeting |
we have implemented it for the resource / command name, and we can apply this mechanism to allow Chinese in other name fields in v3.1 |
Use escaped for message bus topic - service name - profile name - device name Close edgexfoundry#4053 Signed-off-by: bruce <weichou1229@gmail.com>
Opened PRs for this issue, |
Use escaped for message bus topic - service name - profile name - device name Close edgexfoundry#4053 Signed-off-by: bruce <weichou1229@gmail.com>
🚀 Feature Request
Relevant Package [REQUIRED]
This feature request is for...ui-go , core-data, core-metadata, core-command and all device service, those components used package go-mod-core-contracts
Description [REQUIRED]
A clear and concise description of the problem or missing capability...Edgex is used in many traditional industries in China, and many PLC or other device names and addresses are named in Chinese.
Describe the solution you'd like
If you have a solution in mind, please describe it.Modify name regular check in go-mod-core-contracts, and use url.queryUnescape decode those Chinese name in core-metadata, ui-go etc.
Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?The text was updated successfully, but these errors were encountered: