You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today our (JS) APIView parser uses the text property to generate the APIView line for a given item.
This works most of the time, but when you rename an item (either on import or export) the text property will contain the original name instead of the publicly visible name.
In this case, the APIView will show KnownJsonWebKeyEncryptionAlgorithm but we have all the information needed to display the correct name. This issue tracks making changes to the parser to support this scenario.
The text was updated successfully, but these errors were encountered:
### Packages impacted by this PR
@azure/keyvault-keys
### Issues associated with this PR
Resolves#32636Resolves#32751
### Describe the problem that is addressed by this PR
This PR accomplishes two goals:
1. Use generated enum names instead of overwriting them with our
hand-authored ones in keyvault-keys
2. Adds a warning about using RSA1_5 and RSA-OAEP by proxy of (1) -
exposing the generated enum names directly
Note: APIView diff requires a fix to the parser (see Azure/azure-sdk-tools#9768)
Today our (JS) APIView parser uses the
text
property to generate the APIView line for a given item.This works most of the time, but when you rename an item (either on import or export) the
text
property will contain the original name instead of the publicly visible name.Example:
output doc-model from APIExtractor:
In this case, the APIView will show KnownJsonWebKeyEncryptionAlgorithm but we have all the information needed to display the correct name. This issue tracks making changes to the parser to support this scenario.
The text was updated successfully, but these errors were encountered: