{ajv,moment} isn't parseable by eslint

[davfive]

Hi,

I love ajv-moment. However, we're using eslint now and the way its setup to parse the options isn't parseable as valid js. Objects have fields: values, while you're asking for an object that looks like an array.

Could you change it so that it's called like plugin({ ajv: ajv, moment: moment)? or just plugin(ajv, moment)?

Thanks. I'd prefer to use a blessed version rather than forking.

David

[cludden]

@davfive the example in the README is using the ES6 shorthand syntax for object properties covered by the object-shortand ESLint rule. It is perfectly valid to call the plugin using the more verbose syntax for object properties:

import Ajv from 'ajv';
import { plugin } from 'ajv-moment';
import moment from 'moment';

const ajv = new Ajv();
plugin({ ajv: ajv, moment: moment });

[davfive]

Super. Thanks so much. I haven't picked up the ES6 syntax yet. I'll change my code.

On Wed, Oct 3, 2018, 8:32 PM Chris Ludden ***@***.***> wrote: @davfive <https://github.com/davfive> the example in the README is using the ES6 shorthand syntax for object properties covered by the object-shortand ESLint rule <https://eslint.org/docs/rules/object-shorthand>. It is perfectly valid to call the plugin using the more verbose syntax for object properties: import Ajv from 'ajv';import { plugin } from 'ajv-moment';import moment from 'moment'; const ajv = new Ajv();plugin({ ajv: ajv, moment: moment }); — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAwMW9GmXX37Rwwc8Jc9pn3Pz1iswM40ks5uhYFBgaJpZM4XHPRb> .

-- David