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

feature/251 #252

Merged
merged 1 commit into from
Mar 8, 2023
Merged

feature/251 #252

merged 1 commit into from
Mar 8, 2023

Conversation

IshikaGopie
Copy link
Contributor

closes #251

  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • What is the current behavior? (You can also link to an open issue here)

  • What is the new behavior (if this is a feature change)?

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

  • Other information:

…tead of the custom iso 8601 format string that is currently used in the Content Entity
@IshikaGopie IshikaGopie linked an issue Mar 8, 2023 that may be closed by this pull request
4 tasks
@akeemphilbert akeemphilbert merged commit 119e0af into dev Mar 8, 2023
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.

Date fields don't support timezone
2 participants