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, if you call increment_counter on an id that doesn't existing in the table yet, the response is:
{
"status": "error",
"error_message": "The provided expression refers to an attribute that does not exist in the item",
"error_code": "ValidationException",
"error_type": null,
"raw_response": null,
"data": null,
"metadata": null
}
That means you must first call create and give the item a starting number before you can subsequently call increment_counter.
I am thinking it would be nice to handle that inside cruddy. When the above happens, make a subsequent call to create and set the counter_name to whatever the increment is as the initial number.
Thoughts?
The text was updated successfully, but these errors were encountered:
Currently, if you call
increment_counter
on anid
that doesn't existing in the table yet, the response is:That means you must first call
create
and give the item a starting number before you can subsequently callincrement_counter
.I am thinking it would be nice to handle that inside cruddy. When the above happens, make a subsequent call to
create
and set thecounter_name
to whatever the increment is as the initial number.Thoughts?
The text was updated successfully, but these errors were encountered: