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
currently attributes name have a type definition of QueueAttributeName https://github.com/bbc/sqs-consumer/blob/main/src/types.ts#L15C3-L15C17, and missing MessageSystemAttributeName from clinet-sqs, which is actually supported by attributeNames with attributeNames: ['MessageGroupId', 'SentTimestamp'] as any, bypass
Your minimal, reproducible example
Consumer.create with attributeNames: ['MessageGroupId', 'SentTimestamp']
Steps to reproduce
create a consumer via Consumer.create with attributeNames: ['MessageGroupId', 'SentTimestamp']
observer type error
change to attributeNames: ['MessageGroupId', 'SentTimestamp'] as any
observer MessageGroupId actually received with this attribute names
Expected behavior
attributeNames type should support MessageSystemAttributeName from @aws-sdk/client-sqs
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
macOs 14.4.1
Package version
v9.1.0
AWS SDK version
"@aws-sdk/client-sqs": "^3.556.0",
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
currently attributes name have a type definition of QueueAttributeName https://github.com/bbc/sqs-consumer/blob/main/src/types.ts#L15C3-L15C17, and missing MessageSystemAttributeName from clinet-sqs, which is actually supported by attributeNames with
attributeNames: ['MessageGroupId', 'SentTimestamp'] as any
, bypassYour minimal, reproducible example
Consumer.create with attributeNames: ['MessageGroupId', 'SentTimestamp']
Steps to reproduce
Expected behavior
attributeNames type should support MessageSystemAttributeName from @aws-sdk/client-sqs
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
macOs 14.4.1
Package version
v9.1.0
AWS SDK version
"@aws-sdk/client-sqs": "^3.556.0",
Additional context
No response
The text was updated successfully, but these errors were encountered: