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
{{ message }}
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
The table name being operated on is not exposed at runtime through the dyno object. If developers are using TypeScript, the table name is a required part of the update expression. So, to avoid the compilation error, developers must provide their migrations another way to get the table name being worked on - duplicating it with the command line arguments used to invoke dynamodb-migrator.
If the dyno object made the table name string available, we'd be able to avoid this extra step.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The table name being operated on is not exposed at runtime through the dyno object. If developers are using TypeScript, the table name is a required part of the update expression. So, to avoid the compilation error, developers must provide their migrations another way to get the table name being worked on - duplicating it with the command line arguments used to invoke dynamodb-migrator.
If the dyno object made the table name string available, we'd be able to avoid this extra step.
The text was updated successfully, but these errors were encountered: