datetime: forbid using non-integer values in .new()
The patch forbids using non-integer values in datetime constructor `datetime.new()` for `year`, `month`, `day`, `hour`, `min`, `sec`, `usec`, `msec` and `nsec` keys. The type of `tzoffset` can be integer or string, `timestamp` can be double, and integer values allowed in timestamp if `nsec`, `usec`, or `msecs` provided. An error will be raised when a value of incorrect type is passed. Part of #10391 @TarantoolBot document Title: Update types of values passed to `datetime.new()` `datetime.new()` can accept only integer values for `year`, `month`, `day`, `hour`, `min`, `sec`, `usec`, `msec` and `nsec`. The type of `tzoffset` can be integer or string, `timestamp` can be integer or double. (cherry picked from commit cc9010a2b11477b2f16f2b2e168a6b9dcca2fb20)
Showing
- changelogs/unreleased/gh-10391-forbid-non-integers-datetime-new.md 3 additions, 0 deletions...s/unreleased/gh-10391-forbid-non-integers-datetime-new.md
- src/lua/datetime.lua 10 additions, 0 deletionssrc/lua/datetime.lua
- test/app-tap/datetime.test.lua 20 additions, 8 deletionstest/app-tap/datetime.test.lua
Loading
Please register or sign in to comment