[BUG] - historical date type error #1

New Issue

cowch · 2025-11-04T11:32:30-06:00

cowch commented

2025-11-04 11:32:30 -06:00

    ### Describe the bug

    When we go to the url and have 2025-11-01 or 11/1/2025.
    we get 2 different results

    ### Steps to reproduce

In excel or api tool add either date format to reproduce this in the query
BAD way http://usksc1vms006:3000/api/eom/histinv?month=2025-11-01 will show missing data and show stock historical
Good way http://usksc1vms006:3000/api/eom/histinv?month=11/1/2025

    ### Expected behavior

   Both date formats should return the same data no matter the format coming over in the query 

    ### Screenshots

this is the expected return we should get

    ### Gitea Version

    e.g., 1.25.0+rc0

### Describe the bug When we go to the url and have 2025-11-01 or 11/1/2025. we get 2 different results ### Steps to reproduce In excel or api tool add either date format to reproduce this in the query BAD way http://usksc1vms006:3000/api/eom/histinv?month=2025-11-01 will show missing data and show stock historical Good way http://usksc1vms006:3000/api/eom/histinv?month=11/1/2025 ### Expected behavior Both date formats should return the same data no matter the format coming over in the query ### Screenshots this is the expected return we should get ![image.png](/attachments/38e595b4-9183-427d-a52e-6987e21ff5ac) ### Gitea Version e.g., 1.25.0+rc0

image.png

24 KiB

cowch added the bug label 2025-11-04 11:32:30 -06:00

cowch referenced this issue from a commit

2025-11-07 10:09:07 -06:00

fix(historical inv): corrected the way the date can come over to allow for yyyy-mm-dd or with /

cowch closed this issue

2025-11-07 10:09:07 -06:00

Sign in to join this conversation.