slackapi / slackapi/python-slack-sdk
Setting `timezone="UTC"` for `TimePickerElement` should display "UTC" as the "hint" text, not "Monrovia, Reykjavik"
まだ誰も着手していません。
- 主要言語
- Python
- スター
- 4k
- フォーク
- 857
- 平均マージ
- 22時間 21分
- マージ済み PR(30日)
- 16
説明
I am trying to build a form for users to fill out, and it includes a time picker. I want to "force" users to use UTC for this time picker. However, when I set timezone="UTC", the label that is provided is "Monrovia, Reykjavik". This is causing a bunch of downstream confusion that I basically have no control over the representation of.
I could imagine two solutions to this:
- If I supply "UTC" as the timezone, it should just show "Time zone: UTC" as the "hint" under the form field.
- The
TimePickerElementshould allow users to specify its own hint, so that I can display whatever I want, as the builder of the form.
Category (place an x in each of the [ ])
- slack_sdk.web.WebClient (sync/async) (Web API client)
- slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
- slack_sdk.models (UI component builders)
- slack_sdk.oauth (OAuth Flow Utilities)
- slack_sdk.socket_mode (Socket Mode client)
- slack_sdk.audit_logs (Audit Logs API client)
- slack_sdk.scim (SCIM API client)
- slack_sdk.rtm (RTM client)
- slack_sdk.signature (Request Signature Verifier)
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
Start at the TimePickerElement entry point in the slack_sdk.models UI component builders and trace how its timezone value becomes the hint text. Confirm the intended resolution with maintainers, then make the displayed hint represent UTC clearly or support a caller-provided hint, and verify the resulting form-field behavior.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- frontend
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 42/100