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
@praveensri: I'm using the Cosmos DB example to show how you can create a custom built-in connector for Standard logic apps. However, I see that the trigger name in the sample is "Receive document", which doesn't follow the convention for trigger names and sounds more like an action. This inconsistency is very apparent when compared to other Cosmos DB trigger names:
To set up a good model, can we change the name to something like "When a document is received"? That way, if the customer uses the sample code, they get a version that follows the correct naming convention. Thanks!
@praveensri: I'm using the Cosmos DB example to show how you can create a custom built-in connector for Standard logic apps. However, I see that the trigger name in the sample is "Receive document", which doesn't follow the convention for trigger names and sounds more like an action. This inconsistency is very apparent when compared to other Cosmos DB trigger names:
To set up a good model, can we change the name to something like "When a document is received"? That way, if the customer uses the sample code, they get a version that follows the correct naming convention. Thanks!
Here's the file where I found the trigger name:
https://github.com/Azure/logicapps-connector-extensions/blob/CosmosDB/src/CosmosDB/Providers/CosmosDbServiceOperationProvider.cs
The text was updated successfully, but these errors were encountered: