Skip to content

Conversation

@AndyBette
Copy link
Contributor

there's no need for --expression-attribute-names. I also added return-values to demonstrate that the command behaves as expected.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

there's no need for --expression-attribute-names. I also added return-values to demonstrate that the command behaves as expected.
Copy link
Contributor

@tebanieo tebanieo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of removing it I think it will be clearer for users to understand the difference between both approaches and when they need to use # for expression attributes. Please add both explanations.

Don't forget to rebase your branch.

@switch180 switch180 closed this Jul 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants