gr2m / moment-parseformat Goto Github PK

View Code? Open in Web Editor NEW

45.0 6.0 30.0 1.35 MB

A moment.js plugin to extract the format of a date/time string

Home Page: http://gr2m.github.io/moment-parseformat

License: Apache License 2.0

JavaScript 100.00%

moment-parseformat's Introduction

moment.parseFormat – a moment.js plugin

A moment.js plugin to extract the format of a date/time string

Installation

Load via script tag

<script src="moment.js"></script>
<script src="moment.parseFormat.js"></script>

Install using npm for node.js:

npm install --save moment-parseformat

Browser Usage

var format = moment.parseFormat('Thursday, February 6th, 2014 9:20pm'/* , options */);
// dddd, MMMM Do, YYYY h:mma
moment().format(format); // format

Node / CommonJS Usage

var moment  = require 'moment'
var parseFormat = require('moment-parseformat')

var format = parseFormat('Thursday, February 6th, 2014 9:20pm'/* , options */);
// dddd, MMMM Do, YYYY h:mma
moment().format(format); // format

Options

Options can be passed as 2nd parameter

preferredOrder

Type: Object or String

parseFormat tries to figure out the the order of day/month/year by itself if it finds 3 numbers separated by ., - or /. But if it can't, it will fallback to preferredOrder, which can either be set as an object to differentiate by separator, or as a simple string.

Default value:

preferredOrder: {
  '/': 'MDY',
  '.': 'DMY',
  '-': 'YMD'
}

Usage

parseFormat('10.10.2010', {preferredOrder: 'DMY'});
// ☛ DD.MM.YYYY
parseFormat('10.10.2010', {preferredOrder: 'MDY'});
// ☛ MM.DD.YYYY
parseFormat('10.10.2010', {preferredOrder: {
  '/': 'MDY',
  '.': 'DMY',
  '-': 'YMD'
}});
// ☛ MM.DD.YYYY
parseFormat('10/10/2010', {preferredOrder: {
  '/': 'MDY',
  '.': 'DMY',
  '-': 'YMD'
}});
// ☛ DD/MM/YYYY

Fine Print

The moment.parseFormat Plugin have been authored by Gregor Martynus, proud member of the Hoodie Community.

License: MIT

moment-parseformat's People

Contributors

Stargazers

Watchers

moment-parseformat's Issues

Incorrect Date Conversion in nodered, moment.js in javascript works fine.

I posted this on the node-red-contrib-moment github issue board. A awesome contributor pointed me it seems to be an issue with this library. Here is the issue.

TotallyInformation/node-red-contrib-moment#20

Thanks!

2014-01-10 20:00:15 → YYYY-MM-DD H:mm:D

moment.parseFormat('2014-01-10 20:00:15') parsed to YYYY-MM-DD H:mm:D, I expected: <YYYY-MM-DD H:mm:DD>

AFAIKT there are always two digets for seconds. Also, should hours get formated with two digets as well?

PS: Overall - awesome library idea :)

Thursday at 9:20pm

moment.parseFormat('Thursday at 9:20pm') parsed to dddd [at] h:mma, I expected: <please fill in>

https://api.tookanapp.com/ → https://api.tookanapp.com/

moment.parseFormat('https://api.tookanapp.com/') parsed to https://api.tookanapp.com/, I expected: <please fill in>

3/15 → D/YY

moment.parseFormat('3/15') parsed to D/YY, I expected: M/D

Although D/YY is a valid interpretation, it's not the most intuitive one.

npm version 2.1.2 doesn't include index.js

Just upgraded to the latest version of this module and got a resolution error on it. Apparently the NPM version doesn't have the index.js file included.

"2014-02-02T10:11:58+00:00" => YYYY-MM-DDTH:mm:ss+H:mm

moment itself parses this correctly as YYYY-MM-DDTH:mm:ss Z

Su_2016_Aug_3 → Su_YYYY_MMM_D

moment.parseFormat('Su_2016_Aug_3') parsed to Su_YYYY_MMM_D, I expected: dd_YYYY_MMM_D

Library cannot be minified

This library cannot be minified and concatenated with the rest of our dependencies, but when delivered unminified all works well.

05 2015 → DD YYYY

moment.parseFormat('05 2015') parsed to DD YYYY, I expected: MM 2015

Should Be Able to Parse UTC Offsets Without ":"

The UTC Offset for an ISO 8601 formatted date-time includes an optional ":" as noted in Moment's UTC Offset section and Wikipedia's Time zone designators section.

Currently the regexTimezone requires the ":".

Incoming pull request to make the ":" optional.

SUNNYVALE → dddNYVALE

Obviously this isn't a date, because I'm using parseFormat to help look for dates and times in CSV data.
moment.parseFormat('SUNNYVALE') parsed to dddNYVALE, I expected: SUNNYVALE (or null)

I think we should exclude any month/day name or abbrev matches that have adjacent letters.

10/8/2014 5:08:35 PM → M/D/YYYY h:mm:ss a

moment.parseFormat('10/8/2014 5:08:35 PM') parsed to M/D/YYYY h:mm:ss a, I expected: M/D/YYYY h:mm:ss A

August 26, 2014 02:30pm → MMMM D, YYYY h:mma

moment.parseFormat('August 26, 2014 02:30pm') parsed to MMMM D, YYYY h:mma, I expected: MMMM D, YYYY hh:mma

Should default to leading 0's

So I was looking through the regex's and realized that it will only parse timestamps as having a leading 0 if there's an explicit leading 0.

/0\d:\d{2}:\d{2}/

Now this means that it will correctly parse something like 01:33:47 as HH:mm:ss
However once it goes above that to 12:33:47,
it will parse that out as H:mm:ss which is technically correct, as at this point there's no way to know if the timestamp would or would not have a leading 0.

However, I would say that assuming a leading 0 in these caes should be the default, as that is more commonly used with timestamps, and a not leading zero should be the one that is explicitly set,
ie any timestamp like 12:34:56 parses out as HH:mm:ss and the only way to get something as H:mm:ss would be to have a match with something like 1:23:45.

Thursday, February 6th, 2014 9:20pm → dddd, MMMM Do, YYYY h:mma

parsed format is correct, but moment('Thursday, February 6th, 2014 9:20pm', 'dddd, MMMM Do, YYYY h:mma') doesn't parse 6th correctly, Do is not supported for parsing, see moment/moment#1475

format problem

Thursday, February 6th, 2014 9:20pm this format is recognized as invalid by moment.js

15/05/1987 → MM/DD/YYYY

moment.parseFormat('15/05/1987') parsed to MM/DD/YYYY, I expected: <please fill in>

The correct would be DD/MM/YYYY!!

An in-range update of semantic-release is breaking the build 🚨

Version 15.9.6 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	15.9.5
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
✅ coverage/coveralls: First build on greenkeeper/semantic-release-15.9.6 at 99.259% (Details).

Release Notes

v15.9.6

15.9.6 (2018-08-08)

Bug Fixes

do not convert ssh repositoryUrl to https (b895231)

Commits

The new version differs by 3 commits.

b895231 fix: do not convert ssh repositoryUrl to https
8b8e40c docs(plugins): add semantic-release-firefox
06695a1 chore(package): update xo to version 0.22.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Return failure when encountering unknown format

If I use moment.parseFormat('yesterday'), I get a format of 'yesterday'. I'd rather be able to tell that parseFormat didn't recognize the format, for example by returning undefined.

today → today

moment.parseFormat('today') parsed to today, I expected: moment()

3-1-81 → YY-M-D

moment.parseFormat('3-1-81') parsed to YY-M-D, I expected: M-D-YY

Looks like this is still a problem. I checked 9-17-80, and it worked, but I'm guessing that was because of the 17.

31/12/2013 → MM/DD/YYYY

moment.parseFormat('31/12/2013') parsed to MM/DD/YYYY, I expected: DD/MM/YYYY.

Other test cases:

moment.parseFormat('12/31/2013') parsed to MM/DD/YYYY => Correct
moment.parseFormat('31-12-2013') parsed to DD-MM-YYYY => Correct
moment.parseFormat('12-31-2013') parsed to MM-DD-YYYY => Correct

February 6th, 2014 9.20 → MMMM Do, YYYY D.YY

moment.parseFormat('February 6th, 2014 9.20') parsed to MMMM Do, YYYY D.YY, I expected: MMMM Do, YYYY H:mm

Thursday 9:20pm → dddd h:mma

moment.parseFormat('Thursday 9:20pm') parsed to dddd h:mma, I expected: <please fill in>

Doesn't work in the browser when not using require js

@gr2m thanks for this great tool ! however, it does not work in the browser... 😢
i did `bower install moment-parse-format --save'
and the console would show require is not defined.

Simple way to fix it is to put the whole thing in an iife

Thu Feb 04 2016 16:14:40 GMT 0700 → ddd MMM DD YYYY H:mm:ss GMTZ

moment.parseFormat('Thu Feb 04 2016 16:14:40 GMT 0700') parsed to ddd MMM DD YYYY H:mm:ss GMTZ, I expected: ddd MMM DD YYYY H:mm:ss [GMT]Z

01-01-2015 → YYYY-MM-DD

moment.parseFormat('01-01-2015') parsed to YYYY-MM-DD, I expected: MM-DD-YYYY

dependency on moment version

Hello

Is there a reason why your bower packages dependencies refers to moment version 2.5.1?

kind regards

rename repository

Please rename the repository to moment-parseFormat.
Thank you.

1.1.2010 → DD.MM.YYYY

moment.parseFormat('1.1.2010') parsed to DD.MM.YYYY, I expected: D.M.YYYY

2018/12/30 12:00 → YYYY/MM/DD H:mm;

moment.parseFormat('2018/12/30 12:00') parsed to YYYY/MM/DD H:mm, I expected: <please fill in>

Feature request: add hasDate / hasTime / hasDateTime methods for input validations

follow up for #9.

Example

moment.parseFormat.hasDate('yesterday') // false

19-feb-1990 → D-MMMZ

moment.parseFormat('19-feb-1990') parsed to D-MMMZ, I expected: DD-MMM-YYYY

Error when trying to get format for "05/07/2015 12:20:15 UTC"

format.replace(regexFillingWords, '[$1]'))

format.replace is not a function.

06-24-2014 00:28 → YY-MM-DDD H:mm

moment.parseFormat('06-24-2014 00:28') parsed to YY-MM-DDD H:mm, I expected: <MM-DD-YYYY H:mm>

Parsing fractional seconds

Hi,

We really like your library. Thanks for the work. We've noticed that the library doesn't produce the correct output for fractional seconds until the input gets all the way to milliseconds. I have modified the code in my fork so that it will parse tenths and hundredths of a second properly. Would you like me to submit a pull request?

Mike

package.json is missing version

Having trouble working with this package in node because of the missing version.

Should be able to parse ISO-8601 Format

There is currently only support for the following:

2014-02-02T10:11:58+00:00 → YYYY-MM-DDTHH:mm:ssZ

This does not have support for negative offset, or MS.
Forthcoming PR with support for the following:

2014-09-04T01:20:28.888+02:00 → YYYY-MM-DDTHH:mm:ss.SSSZ
2014-09-04T01:20:28.888-02:00 → YYYY-MM-DDTHH:mm:ss.SSSZ
2014-02-02T10:11:58.888Z → YYYY-MM-DDTHH:mm:ss.SSSZ

running this produce error: var format = parseFormat(1397418578);

var format = parseFormat(1397418578);

c:\Users\Idanb11\Work\workspace\node_modules\moment-parseformat\lib\parseformat.js:79
  format = format.replace(regexUnixMillisecondTimestamp, 'x')
                  ^

TypeError: format.replace is not a function
    at parseFormat (c:\Users\Idanb11\Work\workspace\node_modules\moment-parseformat\lib\parseformat.js:79:19)
    at Object.<anonymous> (c:\Users\Idanb11\Work\workspace\server.js:5:14)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)

2014-01-10 20:00:15 → YYYY-MM-DD H:mm:D

moment.parseFormat('2014-01-10 20:00:15') parsed to YYYY-MM-DD H:mm:D, I expected: YYYY-MM-DD H:mm:ss

1-01-2016 → D-MM-YYYY

moment.parseFormat('1-01-2016') parsed to D-M-YYYY, I expected: D-MM-YYYY

2016-07-20 16:33:58+0000 → YYYY-MM-DD H:mm:ss YYYY

moment.parseFormat('2016-07-20 16:33:58+0000') parsed to YYYY-MM-DD H:mm:ss YYYY, I expected: YYYY-MM-DD H:mm:ss+0000

9-17-1980 → D-YY-YYYY

moment.parseFormat('9-17-1980') parsed to D-YY-YYYY, I expected: M-DD-YYYY

Aug 11 2015 11:20p → MMM D YYYY H:mmp

moment.parseFormat('Aug 11 2015 11:20p') parsed to MMM D YYYY H:mmp, I expected: MMM D YYYY h:mma (moment considers a and p valid as well as am and pm)

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Version 15.4.3 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	`semantic-release`
Current Version	15.4.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
✅ coverage/coveralls First build on greenkeeper/semantic-release-15.4.3 at 99.259% Details

Release Notes

v15.4.3

15.4.3 (2018-05-21)

Bug Fixes

package: update marked to version 0.4.0 (a387c04)

Commits

The new version differs by 5 commits.

a387c04 fix(package): update marked to version 0.4.0
228451b docs: fix typo
3503407 docs: clarify which commit types trigger a release
5025fca docs: fix FAQ heading level
6693080 style: fix table indentation

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

gr2m / moment-parseformat Goto Github PK

moment-parseformat's Introduction

moment.parseFormat – a moment.js plugin

Installation

Browser Usage

Node / CommonJS Usage

Options

preferredOrder

Fine Print

moment-parseformat's People

Contributors

Stargazers

Watchers

Forkers

moment-parseformat's Issues

Version 15.9.6 of semantic-release was just published.

15.9.6 (2018-08-08)

Bug Fixes

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

Version 15.4.3 of semantic-release was just published.

15.4.3 (2018-05-21)

Bug Fixes

Recommend Projects

Recommend Topics

Recommend Org

🚨 The automated release from the `master` branch failed. 🚨