nextcloud / nextcloud/context_agent
Improve timezone handling
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 24
- Forks
- 16
- Avg merge
- 7d 20h
- Merged PRs (30d)
- 3
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Currently timezones in the tools are optional and default to UTC, which is not ideal. Either the agent should always ask the user for the timezone, or it should figure out the user's imezone automatically.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating where the tools default timezones to UTC, then clarify whether prompting the user or automatic detection is required. Done means the chosen timezone behavior is specified and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100