Some questions regarding durations

未關閉
#67 7 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
28/100
Issue 類型
文件
描述清晰度
基本清楚
活躍度
停滯
領域
documentation

研究方向

Start by comparing the documented roles of Data.Time.Duration and Data.Interval.Duration, then check which Pursuit documentation is outdated relative to the current package. The issue also asks about human-readable multi-unit formatting, but gives no files, tests, or agreed scope for that work. Done would require clarifying the duration distinction, updating the documentation, and deciding whether formatting belongs in this package; the thread has had no recent activity.

由索引模型根據 Issue 內容生成。

描述

status: needs more info
  1. There is Data.Time.Duration and also Data.Interval.Duration and I wonder what the difference is. Data.Time.Duration is used for functions like adjust and diff, while Data.Interval.Duration seems to be mostly about parsing and formatting of ISO8601 durations? Is one of them deprecated? Is there a conceptual difference that I fail to see?

  2. Is there a way to format durations in a human-readable fashion? E.g. neither "643257 milliseconds" nor "0,051 days" but in a multi-unit format like "2 days, 15h, 45min"? (this is probably related to purescript formatters, but the calculation might belong to this package)

  3. I realized that the documentation in Pursuit is not up-to-date (the latest version is 3.2.0). Could somebody please update it?

主要語言
PureScript
星號
51
分支
48
平均合併
2 天 23 小時
30 天內合併 PR
1

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

purescript/purescript-datetime 的其他 Issue

查看 purescript/purescript-datetime 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。