Closed EgleHelms closed 5 months ago
@Catharsis68 please add here if you have anything more to add.
@xquanluu can you try to recreate?
Hi @davehorton
case 1: Could you send me in private Message for a credential with deployment ID. case 2: fixed, PR is in draft version case 3: This is exactly the same the case we add one service provider level google credential without label and add another account level google credential without label. API server and feature server will choose account level first, if there is no account level credential, it will choose service provider level.
@xquanluu for testing case 1, do you really need a valid deployment ID? It seems like you could still test it with an invalid deployment id
Hi @davehorton @EgleHelms The PR fixes Case 1 and Case 2.
For Case 3 Could you please check my previous comment?
for now I thinkk case 3 is a suggested enhancement, not a bug so I am merging this
Case 1 Repro steps:
Result: preselected label will be "None" but the "Voice" will not appear as a text field for custom voice
Also, I think voice field should only show a placeholder, it should not have a voice prefilled, because this is misleading. From what I have tested so far, the MS credentials that will hold custom voice will not have other voices available, so this field should not be prefilled, just have a placeholder
Case 2
Result: the label1 will still be as label in the api-server
Case 3: it is currently possible to have credentials without labels in the same level (account or all accounts) as well as on both. No way it is possible to know what will be applied. I think it should not be allowed to have no label 2 times regardless of level.
======= In addition we need to make sure none of the other cases are broken:
Standard Cases:
Could also be an improvement to list the labels, speech providers alphabetically.