Throw `GitHubProjectInvalidValueError` error when date field is set to invalid value
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
### Please avoid duplicates
- [X] I checked [all open bugs](https://github.com/gr2m/github-project/issues?q=is%3Aissue+is%3Aopen+label%3Abug) and none of them matched my problem.
### Reproducible test case
_No response_
### Please select the environment(s) that are relevant to your bug report
- [X] Browsers
- [X] Node
- [X] Deno
### Versions
v5.3.1
### What happened?
```
GraphqlResponseError: Request failed due to following response errors:
- Column value must be a valid value for date column
```
We should instead throw a `GitHubProjectInvalidValueError`
### Would you be interested in contributing a fix?
- [ ] yes
Contributor guide
Research direction
Start by locating the date-field handling and the code that currently surfaces GraphqlResponseError for invalid column values. Reproduce the reported invalid-date case in the browser, Node, or Deno environment, then verify that it raises GitHubProjectInvalidValueError instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, graphql, javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100