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
Thank you for contributing to the design guidelines for Azure SDKs. We welcome all discussions and contributions. Since the design guidelines affect the client libraries for all Azure services, we thoroughly discuss and vet any design guideline changes before we incorporate them into the official guidance. This process can take some time, so your patience is appreciated.
** Before submitting, ensure you adjust the title of the issue appropriately **
The Basics
Which design guideline is affected?
Connection String support
Which target languages are affected?
All languages
Describe the change:
Make the form of the connection string specific. For example, we don't want individual services to "create" a connection string that has special functionality. (e.g. support for developer connection strings for storage).
Reasoning
Connection string support needs to be consistent. The current guidelines provide too much flexibility which will result in inconsistencies between services.
Please provide any additional detail or reasoning for the request.
The text was updated successfully, but these errors were encountered:
Board does not think we should be doing strongly typed connection strings.
We already have guidelines around requirements for connection strings - explicitly, the connection string must be copied from the portal / tooling.
Thank you for contributing to the design guidelines for Azure SDKs. We welcome all discussions and contributions. Since the design guidelines affect the client libraries for all Azure services, we thoroughly discuss and vet any design guideline changes before we incorporate them into the official guidance. This process can take some time, so your patience is appreciated.
** Before submitting, ensure you adjust the title of the issue appropriately **
The Basics
Connection String support
All languages
Make the form of the connection string specific. For example, we don't want individual services to "create" a connection string that has special functionality. (e.g. support for developer connection strings for storage).
Reasoning
Connection string support needs to be consistent. The current guidelines provide too much flexibility which will result in inconsistencies between services.
Please provide any additional detail or reasoning for the request.
The text was updated successfully, but these errors were encountered: