-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug Report: Documentation Models Attribute Datetime #5272
Comments
@YaMiSt thanks for creating this issue! 🙏🏼 You are correct! It looks like the example is incorrect here: appwrite/src/Appwrite/Utopia/Response/Model/AttributeDatetime.php Lines 20 to 25 in 6122a25
I think the |
I want to work on this Issue. Please assign it to me. |
@stnguyen90 raised PR as per the suggested changes |
@rinkuhasija, assigned! Thanks for your interest! 🙏🏼 @imtushardave, to be considerate of others, we try to assign on a first-come, first-serve basis. If @rinkuhasija isn't able to submit a PR, I'll reassign this issue to you. |
No issues @stnguyen90, I really appreciate your consideration for each contributer. |
@stnguyen90 raised a PR that fixes this Issue. |
I am closing this PR as @rinkuhasija has raised PR for the same. Happy contributing! |
@Haimantika Closing. Thanks @rinkuhasija for the PR |
👟 Reproduction steps
Go to: https://appwrite.io/docs/models/attributeDatetime
I think the example on the website is wrong, because I got an error from appwlite cli:
{ "key": "birthDay", "type": "2020-10-15T06:38:00.000+00:00", "status": "available", "required": true, "array": false, "format": "datetime", "default": "2020-10-15T06:38:00.000+00:00" }
👍 Expected behavior
It should be (is there a format possible?):
{ "key": "birthDay", "type": "datetime", "status": "available", "required": true, "array": false, "default": "2020-10-15T06:38:00.000+00:00" }
👎 Actual Behavior
Actually i got an error from the console.
🎲 Appwrite version
Version 1.2.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: