aws-amplify / aws-amplify/amplify-studio

Admin UI improperly handles the AWSDateTime type

Open
#70 4 comments 0 reactions 0 assignees View on GitHub
data feature-request studio-ui
Dominant language
No language data
Stars
135
Forks
32
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

The Admin UI improperly handles the AWSDateTime type:

* The user is only allowed to enter hours and minutes
![image](https://user-images.githubusercontent.com/9916473/103464625-3c7d0900-4d03-11eb-97ba-dbdd691e7af3.png)

* When the data is saved, the entered time is recorded as UTC time
![image](https://user-images.githubusercontent.com/9916473/103464647-6b937a80-4d03-11eb-89d6-5af02330a2a5.png)

**Expected behavior**
The user should be able to enter a full time string, in any of the supported formats.
* hh:mm:ss.sssZ
* hh:mm:ssZ
* hh:mmZ
* hh:mm:ss.sss±hh:mm:ss
* hh:mm±hh:mm
* etc.

**Desktop (please complete the following information):**
- OS: Windows 10
- Browser: Firefox
- Version: 84.0.1

Contributor guide

Open the contributing guide

Research direction

Start by locating the Admin UI input handling for the AWSDateTime type and reproduce the reported behavior in Firefox using the formats listed in the issue. Done means users can enter each supported full time string and saving preserves the entered timezone and precision rather than recording only UTC hours and minutes.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.