Skip to content

Fix type validations being to strict for dates#6453

Merged
sushantdhiman merged 2 commits intosequelize:v3from
fintura:fix-dates
Aug 19, 2016
Merged

Fix type validations being to strict for dates#6453
sushantdhiman merged 2 commits intosequelize:v3from
fintura:fix-dates

Conversation

@BridgeAR
Copy link
Copy Markdown
Contributor

@BridgeAR BridgeAR commented Aug 17, 2016

Pull Request check-list

  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Does your issue contain a link to existing issue (Closes #[issue]) or a description of the issue you are solving?
  • Have you added new tests to prevent regressions?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Have you added an entry under Future in the changelog?

Description of change

Currently the type validations for dates are very strict. Most of the type validations accept strings as input and this should also be the case for dates as far as I see it.

@janmeier
Copy link
Copy Markdown
Member

LGTM - Needs a rebase

@janmeier
Copy link
Copy Markdown
Member

Do you mind creating this for the master branch as well?

@BridgeAR
Copy link
Copy Markdown
Contributor Author

Done

@felixfbecker
Copy link
Copy Markdown
Contributor

LGTM

@sushantdhiman sushantdhiman merged commit 6e44b59 into sequelize:v3 Aug 19, 2016
holm pushed a commit to peakon/sequelize that referenced this pull request Aug 19, 2016
* Fix type validations being to strict for dates

* Add changelog entry
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.

4 participants