[BUG] Missing timezones when creating lodging entry
Closed this issue ยท 0 comments
Alchez commented
๐ Bug Description
While creating a lodging in my local timezone (Asia/Kolkata), I get the following error in the API call: "Asia/Kolkata" is not a valid choice.
๐ Steps to Reproduce
Steps to reproduce the behavior:
- Create a new lodging entry modal
- In the "Date Information" section, set the timezone to "Asia/Kolkata"
- Try to save the lodging
- Observe the error
โ Expected Behavior
Lodging gets created with the check-in and check-out times set in the provided timezone.
๐ณ Environment Details
- Platform: Docker
- Install Method: Docker Compose
- AdventureLog Version: 0.11.0
- Reverse Proxy: None
๐ Additional Context
- This seems to be happening because timezones are being provided by two different sources:
- In the frontend, the timezone selector uses the
IntlAPIs to populate the timezone values - In the backend, there is a hard-coded set of values accessed from the
timezones.pyfile.
- In the frontend, the timezone selector uses the
- The issue above happens because the backend expects a value of
Asia/Calcutta(the old name of the city) whereas the frontend is sendingAsia/Kolkata(the new name of the city).