You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/11/09 14:43:47 UTC

[GitHub] [shardingsphere-ui] wqzwh opened a new issue #62: sharding-ui-frontend optimization correlation

wqzwh opened a new issue #62:
URL: https://github.com/apache/shardingsphere-ui/issues/62


   The optimization is as follows:
   
   - [x] 1. Click Add a registry, the orchestration Name in the table has a line break, and the problem of letters'case unity
   
   - [x] 2. Copyright deletes year information and adds UI version number, 2018?
   
   Copyright_The Apache Software Foundation, Licensed under the Apache License, Version 2.0, UI Version 1.0.0.
   
   - [x] 3. Rename the left label bar
   
   Config reigst--Registry Center
   Config Mangage--Rule Config
   Orchestration--Runtime Status
   
   - [x] 4. The switch button in the operation of Config regit, together with the floating prompt, indicates that: Activate
   
   - [x] 5. Does the "Namespaces" tag on the config registration page imply that multiple namespaces can be filled in? How to fill in?
   
   - [x] 6. orchestration page - slave data Source info tag, click the error report as follows:
   
   Cannot create property = encryptors for JavaBean = org. apache. shardingsphere. core. yaml. config. sharding. YamlSharding Rule Configuration@4ea571e8 in'string', line 1, column 1: encryptors: ^ Unable to find property'encryptors'on class: org. apache. shardingsphere. core. yaml. g. sharding. YamlSharding. RumlConfiguration' in'string', line 2, line 3, line 1: encryptors: ^ Unable to find property'encryptors'on class: org. Apache shardingsphere. core. yaml. Tor_aes: ^
   
   - [x] 7. When only one config exists, you can only click the "Activate" button once in the operation, and it has been graying and unable to operate since then.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org