We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
const document = await databases.createDocument( import.meta.env.VITE_APPWRITE_EVENTS_DATABASE_ID, import.meta.env.VITE_APPWRITE_EVENTS_COLLECTION_ID, ID.unique(), { ..., date: new Date().toISOString(), ... } );
My Solution: If I remove the Z at end of datetime, document is then correctly created
const document = await databases.createDocument( import.meta.env.VITE_APPWRITE_EVENTS_DATABASE_ID, import.meta.env.VITE_APPWRITE_EVENTS_COLLECTION_ID, ID.unique(), { ..., date: new Date(target.date.value).toISOString().slice(0, -1), ... } );
New document in collection will be created.
Gives a 500 server error
Version 0.10.x
Linux
No response
The text was updated successfully, but these errors were encountered:
@destocot, thanks for creating this issue! 馃檹 Were you using the web sdk or node SDK?
Also, what version of the SDK?
Sorry, something went wrong.
@stnguyen90 apologies for any confusion but it was the
web sdk | "appwrite": "^13.0.1",
@destocot, sorry for the delay. I just tested with version 13.0.1 of the SDK with code like:
let promise = databases.createDocument('default', 'test', 'unique()', { 'dt': new Date().toISOString(), 'searchAttribute': 'a new task', });
and this worked fine for me:
What's the payload tab look like for you in your browser's dev tools?
stnguyen90
No branches or pull requests
馃憻 Reproduction steps
My Solution: If I remove the Z at end of datetime, document is then correctly created
馃憤 Expected behavior
New document in collection will be created.
馃憥 Actual Behavior
Gives a 500 server error
馃幉 Appwrite version
Version 0.10.x
馃捇 Operating system
Linux
馃П Your Environment
No response
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: