You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wrong Date Logic: The formatDate function uses 0-indexed months. This causes the library to query the wrong date when verifying service usage (e.g., searching for April instead of May).
Confusing Error Crashes: When an API call fails, the library crashes with a generic SyntaxError: Unexpected end of JSON input. This masks the actual error message from the server, making it hard to debug.
Typos: Several error messages .
The Impact
Users get incorrect "0" counts when checking service usage for a specific date.
Developers cannot easily tell why an artifact import failed because the real error is hidden.
Proposed Solution
Update formatDate to use 1-indexed months and proper padding.
Update error handlers to capture and report the raw error text from the server.
Add tests that specifically use Date objects to prevent this bug from returning.
The Problem
formatDatefunction uses 0-indexed months. This causes the library to query the wrong date when verifying service usage (e.g., searching for April instead of May).SyntaxError: Unexpected end of JSON input. This masks the actual error message from the server, making it hard to debug.The Impact
Proposed Solution
formatDateto use 1-indexed months and proper padding.Dateobjects to prevent this bug from returning.