Constrain Parsed Error to Swift Error

[ajevans99]

Description

This PR updates the Parsed<Value, Error> enum to constrain the Error generic to conform to Swift.Error. This change ensures semantic clarity, improves type safety, and enables better integration with Swift’s error-handling mechanisms.

Closes #56

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Additional Notes

Add any other context or screenshots about the pull request here.

---

Note: You can add the auto-format label to this pull request to enable automatic Swift formatting.

[gsabran]

Thanks!

What do you think of also adding a conformance to LocalizedError ? I tried to gave it a go, but for some cases I was not sure what was the best description:

extension ParseIssue: LocalizedError {
  public var errorDescription: String? {
    switch self {
      case typeMismatch(let expected, let actual):
        return "Type mismatch. Expecting \(expected.rawValue) and got \(actual.primative.rawValue): \(actual.description.prefix(20)"
      case noEnumCaseMatch(let value):
        return ...
      case missingRequiredProperty(let property)
        return "Missing required property `\(property)`"
      case compactMapValueNil(let value)
        return ...
      case compositionFailure(let type, let reason, let nestedErrors)
        return ...
    }
  }
}

[ajevans99]

How about this? Conform to CustomStringConvertible

I'm not sure about using LocalizedError in the library like that. I'm trying to avoid a dependency on Foundation (with the exception of URL in validation) and I think it might be a bit misleading since the values are not actually localized. Also, this is more consistent with ValidationIssue.

[gsabran]

This is great!