-
Notifications
You must be signed in to change notification settings - Fork 68
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
Portal: We should add a text indicating the connection string and key type/value should be presented in a fixed order (Primary, Secondary) #24
Comments
Alternatively, we can have "Primary Connection String", "Secondary Connection String" etc. |
it seems the issue with the secondary key before the primary key is fixed, I can't reproduce it. |
The subtitles "Primary", "Secondary", and corresponding RO values come from the server ... |
The key name order follows the order keys are recreated, it should be a fixed order. And the string that comes from the server needs to be translated into one provided by the portal (localizable and containing the connection string words). |
The service (RP) won't guarantee the order of keys and the portal should not depend on it. Therefore, the portal should
|
Fixed committed. |
We should have "Connection String" in front of the connection string box.
![image](https://user-images.githubusercontent.com/10566826/51945513-c9aadb00-23d3-11e9-9294-7dd66a34fc2c.png)
In addition, in the screenshot above, the "Secondary" comes before the "Primary", which sounds like another bug.
The text was updated successfully, but these errors were encountered: