histropediajs 1.6.0 → 1.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/README.md +1 -0
  2. package/dist/histropedia.esm.js +1859 -1858
  3. package/dist/histropedia.umd.js +1867 -1866
  4. package/dist/histropedia.umd.min.js +2 -2
  5. package/index.d.ts +6 -1
  6. package/package.json +1 -1
package/README.md CHANGED
@@ -118,6 +118,7 @@ Each article (event) uses the following minimal shape. Short property aliases ar
118
118
  Notes:
119
119
 
120
120
  - BCE years are supported with negative year values; internally year 0 represents 1 BCE. Set `shiftBceDates: true` to shift year input by 1 so that -1 is 1BCE.
121
+ - When `precision` is omitted from a date-parts object, the smallest supplied time component determines precision (`millisecond`, `second`, `minute`, then `hour`), including zero values. Objects without time components still default to day precision, including year-only and year/month objects. Explicit `precision` always overrides inference.
121
122
  - Precision accepts `millisecond`, `second`, `minute`, `hour`, `day`, `month`, `year`, `decade`, `century`, `millennium`, `million-years`, and `billion-years`. The exported `Histropedia.PRECISION_*` constants resolve to these strings. Legacy numeric precision values remain supported but are deprecated.
122
123
  - If `to` is omitted and `isToPresent` is false, the article is treated as an instant event (uses `from`), but the `from.precision` determines the span of the period line.
123
124
  - Full precision boundary rules and examples: [docs/date-precision.md](docs/date-precision.md)