Invalid paths
type | https://docs.frem.sh/reference/api/errors/invalid-paths |
| HTTP status | 400 Bad Request |
What it means
The request was malformed, or a field failed validation. Returned by the Active work read endpoints (list_active_work, find_related_work).
Example detail messages returned with this error:
pathsis a comma-separated list of at most 100 repository paths.
What to do
Send at most 100 repository paths, comma-separated, each at most 500 characters. Only their top-level folders or modules are compared.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/invalid-paths",
"title": "Bad Request",
"status": 400,
"detail": "..."
}Branch on type, not on title or detail - those are human-readable and may be reworded.