Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix parse regex bug #1307

Merged
merged 1 commit into from
Jan 4, 2021
Merged

fix: fix parse regex bug #1307

merged 1 commit into from
Jan 4, 2021

Conversation

iamkun
Copy link
Owner

@iamkun iamkun commented Jan 4, 2021

fix #1305

@codecov
Copy link

codecov bot commented Jan 4, 2021

Codecov Report

Merging #1307 (e0dc6a4) into dev (90bb665) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##               dev     #1307   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          175       175           
  Lines         1697      1697           
  Branches       387       387           
=========================================
  Hits          1697      1697           
Impacted Files Coverage Δ
src/plugin/localeData/index.js 100.00% <ø> (ø)
src/constant.js 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b60466e...e0dc6a4. Read the comment docs.

@iamkun iamkun merged commit 9ef1714 into dev Jan 4, 2021
iamkun added a commit that referenced this pull request Jan 4, 2021
iamkun pushed a commit that referenced this pull request Jan 5, 2021
## [1.10.2](v1.10.1...v1.10.2) (2021-01-05)

### Bug Fixes

* fix parse regex bug ([#1307](#1307)) ([db2b6a5](db2b6a5)), closes [#1305](#1305)
* remove module entry in package.json to revert 1.10.1 change ([#1314](#1314)) ([824dcb8](824dcb8))
* update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](#1315)) ([b0dda31](b0dda31))
@iamkun iamkun deleted the fix/regex-parse-bug branch May 26, 2021 06:57
andrewhood125ruhuc added a commit to andrewhood125ruhuc/SidRH2 that referenced this pull request May 10, 2022
## [1.10.2](iamkun/dayjs@v1.10.1...v1.10.2) (2021-01-05)

### Bug Fixes

* fix parse regex bug ([#1307](iamkun/dayjs#1307)) ([db2b6a5](iamkun/dayjs@db2b6a5)), closes [#1305](iamkun/dayjs#1305)
* remove module entry in package.json to revert 1.10.1 change ([#1314](iamkun/dayjs#1314)) ([824dcb8](iamkun/dayjs@824dcb8))
* update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](iamkun/dayjs#1315)) ([b0dda31](iamkun/dayjs@b0dda31))
andrewhood125ruhuc added a commit to andrewhood125ruhuc/SidRH2 that referenced this pull request May 10, 2022
## [1.10.2](iamkun/dayjs@v1.10.1...v1.10.2) (2021-01-05)

### Bug Fixes

* fix parse regex bug ([#1307](iamkun/dayjs#1307)) ([db2b6a5](iamkun/dayjs@db2b6a5)), closes [#1305](iamkun/dayjs#1305)
* remove module entry in package.json to revert 1.10.1 change ([#1314](iamkun/dayjs#1314)) ([824dcb8](iamkun/dayjs@824dcb8))
* update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](iamkun/dayjs#1315)) ([b0dda31](iamkun/dayjs@b0dda31))
splashwizard pushed a commit to splashwizard/tracking-time that referenced this pull request Oct 21, 2024
## [1.10.2](iamkun/dayjs@v1.10.1...v1.10.2) (2021-01-05)

### Bug Fixes

* fix parse regex bug ([#1307](iamkun/dayjs#1307)) ([db2b6a5](iamkun/dayjs@db2b6a5)), closes [#1305](iamkun/dayjs#1305)
* remove module entry in package.json to revert 1.10.1 change ([#1314](iamkun/dayjs#1314)) ([824dcb8](iamkun/dayjs@824dcb8))
* update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](iamkun/dayjs#1315)) ([b0dda31](iamkun/dayjs@b0dda31))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Converting an timezoned instance to another timezone returns the wrong result
1 participant