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
In our app we publish different message types on the same channel from different functions. This all works fine if all the functions are on the same class...
[AsyncApi("Primary")]
[Channel(HubNames.CUSTOMERS)]
[SubscribeOperation()]
public class FuncCustomersUpdates
{
[Message(typeof(CustomerUpdateEventResource), MessageId = Profiles.CUSTOMER_EVENTS_UPDATE, Title = "Customer Update")]
[FunctionName(nameof(PublishCustomerUpdateEvents))]
public async Task<PublishCustomerUpdateEventsResult> PublishCustomerUpdateEvents(
...
[Message(typeof(CustomerAddressUpdateEventResource), MessageId = Profiles.CUSTOMER_ADDRESS_EVENTS_UPDATE, Title = "Customer Address Update")]
[FunctionName(nameof(PublishCustomerAddressUpdateEvents))]
public async Task<PublishCustomerAddressUpdateEventsResult> PublishCustomerAddressUpdateEvents(
...
}
but we do this in azure functions where it's nicer to have these as distinct function classes for different message types we publish. So very similar to #133 i would like it if we could support multiple channel/subscribe pairs across classes. eg
[AsyncApi("Primary")]
[Channel(HubNames.CUSTOMERS)]
[SubscribeOperation()]
public class FuncCustomerUpdates
{
[Message(typeof(CustomerUpdateEventResource), MessageId = Profiles.CUSTOMER_EVENTS_UPDATE, Title = "Customer Update")]
[FunctionName(nameof(PublishCustomerUpdateEvents))]
public async Task<PublishCustomerUpdateEventsResult> PublishCustomerUpdateEvents(
...
}
[AsyncApi("Primary")]
[Channel(HubNames.CUSTOMERS)]
[SubscribeOperation()]
public class FuncCustomerAddressUpdates
{
[Message(typeof(CustomerAddressUpdateEventResource), MessageId = Profiles.CUSTOMER_ADDRESS_EVENTS_UPDATE, Title = "Customer Address Update")]
[FunctionName(nameof(PublishCustomerAddressUpdateEvents))]
public async Task<PublishCustomerAddressUpdateEventsResult> PublishCustomerAddressUpdateEvents(
...
}
workaroudn is to make them the same partial class...which is ok but not the long term solutoin we are after
The text was updated successfully, but these errors were encountered:
In our app we publish different message types on the same channel from different functions. This all works fine if all the functions are on the same class...
but we do this in azure functions where it's nicer to have these as distinct function classes for different message types we publish. So very similar to #133 i would like it if we could support multiple channel/subscribe pairs across classes. eg
workaroudn is to make them the same partial class...which is ok but not the long term solutoin we are after
The text was updated successfully, but these errors were encountered: