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

GraphQL Dates not using the right format #26890

Closed
erickgonzalez opened this issue Dec 5, 2023 · 1 comment · Fixed by #27116
Closed

GraphQL Dates not using the right format #26890

erickgonzalez opened this issue Dec 5, 2023 · 1 comment · Fixed by #27116
Assignees
Labels
LTS: Excluded Ticket that has been excluded from at least one LTS OKR : Customer Support Owned by Scott QA : Approved Release : 23.01.10 Included in LTS patch release 23.01.10 Release : 23.10.24 v1 Included in LTS patch release 23.10.24 v1 Release : 24.01.26 Bug Fixing Team : Bug Fixers Type : Defect

Comments

@erickgonzalez
Copy link
Contributor

erickgonzalez commented Dec 5, 2023

Parent Issue

No response

Problem Statement

When using GraphQL to pull up Date Fields, the format is wrong.

Steps to Reproduce

1- Navigate to the GraphQL Portlet
2- Run the following query:

query ContentAPI {
  BlogCollection(query: "", limit: 1, offset: 0, sortBy: "score") {
    title
    modDate
    postingDate
  }
}

3- Check the date format, for modDate comes as it should but Date Fields don't:

{
        "title": "test blog new",
        "modDate": "2023-12-05 21:35:04.675",
        "postingDate": "Tue Dec 05 21:34:00 UTC 2023"
      },

Acceptance Criteria

Date Field format should be the same as the modDate

{
        "title": "test blog new",
        "modDate": "2023-12-05 21:35:04.675",
        "postingDate": "2023-12-05 21:34:00.000"
      },

dotCMS Version

23.01 +

Proposed Objective

Customer Success

Proposed Priority

Priority 1 - Show Stopper

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.zendesk.com/agent/tickets/114381

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@erickgonzalez erickgonzalez self-assigned this Dec 5, 2023
erickgonzalez added a commit that referenced this issue Dec 5, 2023
@erickgonzalez erickgonzalez added Team : Bug Fixers OKR : Customer Success Owned by Arno OKR : Customer Support Owned by Scott LTS : Next Ticket that will be added to LTS Release : 23.10.24 v1 Included in LTS patch release 23.10.24 v1 and removed Triage labels Dec 6, 2023
@erickgonzalez erickgonzalez removed the OKR : Customer Success Owned by Arno label Dec 19, 2023
erickgonzalez added a commit that referenced this issue Dec 27, 2023
@erickgonzalez erickgonzalez added Next LTS Release and removed LTS : Next Ticket that will be added to LTS labels Dec 27, 2023
@erickgonzalez erickgonzalez linked a pull request Dec 28, 2023 that will close this issue
@erickgonzalez erickgonzalez added the LTS: Excluded Ticket that has been excluded from at least one LTS label Dec 28, 2023
erickgonzalez added a commit that referenced this issue Dec 28, 2023
@erickgonzalez erickgonzalez added the Release : 23.01.10 Included in LTS patch release 23.01.10 label Jan 2, 2024
github-merge-queue bot pushed a commit that referenced this issue Jan 2, 2024
* fix: convert to Timestamp ref: #26890

* tests ref: #26890
@erickgonzalez erickgonzalez reopened this Jan 2, 2024
@josemejias11
Copy link

Approved: Tested on master_cf9b773, Docker, macOS 13.0, FF v113.0
Screenshot 2024-01-10 at 9 31 06 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LTS: Excluded Ticket that has been excluded from at least one LTS OKR : Customer Support Owned by Scott QA : Approved Release : 23.01.10 Included in LTS patch release 23.01.10 Release : 23.10.24 v1 Included in LTS patch release 23.10.24 v1 Release : 24.01.26 Bug Fixing Team : Bug Fixers Type : Defect
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants