Request clearer error message than "Error: invalid input: input is not string"
See original GitHub issueError: invalid input: input is not string
seems to happen in a number of situations, an this error message on its own is not enough to determine what the problem is.
For example
const document = { id: 'amazing', content: 'Hello Miss Amazing!' };
const { body } = await container.items.upsert(document);
This works in one example and not in another … it makes me think the doc content is invalid, but it’s not clear if it means the values in the doc, the doc itself, the container … or something else.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
DocumentDB - The input name is invalid. Ensure to provide a ...
The input name "123456" is invalid. Ensure to provide a unique non-empty string less than '255' characters.","The request payload is ...
Read more >New code. How can I display an error message if the user ...
I just need to put an error message if the user entered a non-parenthesis character. Thank you in advance. I need help in...
Read more ><input>: The Input (Form Input) element - HTML
The <input> HTML element is used to create interactive controls for web-based forms in order to accept data from the user; a wide...
Read more >Proposed Error message describes invalid form field value
This rule checks that text error messages provided when the user completes a form field ... This input element does not have a...
Read more >7.16 — std::cin and handling invalid input - Learn C++
Since strings do not have any restrictions on what characters can be ... We can generally separate input text errors into four types:....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
it may be related to when i connect with a db id vs a database object with an id property.
Report the issue at here