umgeher/qdate
0
Fork 0
Code Issues Pull requests Releases Activity

Merge pull request #42 from kianmeng/fix-typos

Browse source 
Fix typos
This commit is contained in:
Jesse Gumm 2022-01-28 08:33:04 -06:00 • committed by GitHub
commit 357b5844eb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
CHANGELOG.markdown
View file

@ -22,7 +22,7 @@
just the opposite of `beginning_X`) just the opposite of `beginning_X`)
* Add `between/[2,3,5]` functions for computing whether a date/time is between * Add `between/[2,3,5]` functions for computing whether a date/time is between
two others. two others.
* Update to rebar3 and add hex compatability. (@Licenser) * Update to rebar3 and add hex compatibility. (@Licenser)
* Properly add dependent apps to .app.src (@Licenser) * Properly add dependent apps to .app.src (@Licenser)
* Add an optional "relative date/time parser". * Add an optional "relative date/time parser".
* Fix: Ensure `get_timezone()` returns the default timezone (from config) if it * Fix: Ensure `get_timezone()` returns the default timezone (from config) if it

6
README.markdown
View file

@ -107,7 +107,7 @@ will infer the timezone in the following order.
#### Disambiguating Ambiguous Timezone Conversions #### Disambiguating Ambiguous Timezone Conversions
Sometimes, when youre converting a datetime from one timezone to another, there Sometimes, when you're converting a datetime from one timezone to another, there
are potentially two different results if the conversion happens to land on in a are potentially two different results if the conversion happens to land on in a
timezone that's in the middle of a Daylight Saving conversion. For example, timezone that's in the middle of a Daylight Saving conversion. For example,
converting "11-Nov-2013 1:00:am" in "America/New York" to "GMT" could be both converting "11-Nov-2013 1:00:am" in "America/New York" to "GMT" could be both
@ -536,7 +536,7 @@ qdate:between(qdate:add_minutes(-15), Date, qdate:add_minutes(15)).
%% But, you don't have to: if that's a common format you use in your %% But, you don't have to: if that's a common format you use in your
%% application, you can register your format with the `qdate` server, and then %% application, you can register your format with the `qdate` server, and then
%% easiy refer to that format by its key. %% easily refer to that format by its key.
%% So let's take that format and register it %% So let's take that format and register it
16> qdate:register_format(longdate, "l, F jS, Y g:i A T"). 16> qdate:register_format(longdate, "l, F jS, Y g:i A T").
@ -720,7 +720,7 @@ the week" calculation. This has three forms, specifically:
7=Sunday). 7=Sunday).
+ `beginning_week(DayOfWeek, Date)` - Calculates the beginning of the week + `beginning_week(DayOfWeek, Date)` - Calculates the beginning of the week
based on the provided `DayOfWeek`. Valid values for DayOfWeek are the based on the provided `DayOfWeek`. Valid values for DayOfWeek are the
integers 1-7 or the atom verions of the days of the week. Specifically: integers 1-7 or the atom versions of the days of the week. Specifically:
* Monday: `1 | monday | mon` * Monday: `1 | monday | mon`
* Tuesday: `2 | tuesday | tue` * Tuesday: `2 | tuesday | tue`