log1st Comments - Answer Overflow

So, theoretically, I can use error.path and error.input for storing data during serialization. As long as the Traversal config is the same between the serializer and deserializer, I see that these fields, along with data, can be removed from the object. The only problem is that I’m not sure how to properly deserialize it back while keeping all the internal logic working as expected.

10 replies

Aarktype

•Created by log1st on 2/13/2025 in #questions

ArkErrors serialization/deserialization

As i see there's ArkError:input field in each object and it depends on the rule that failed validation. eg. "string > 2" in case of failure contains

input = {
  code: 'minLength',
  description: 'at least length 2',
  meta: {},
  rule: 2
}

input = {
  code: 'minLength',
  description: 'at least length 2',
  meta: {},
  rule: 2
}

10 replies

Aarktype

•Created by log1st on 2/13/2025 in #questions

ArkErrors serialization/deserialization

yup, that's not what i'm looking for. my goal is to serialize and deserialize whole ArkErrors object.

10 replies

Aarktype

•Created by log1st on 2/13/2025 in #questions

ArkErrors serialization/deserialization

Or am I that blind? 🙂

10 replies

Aarktype

•Created by log1st on 2/13/2025 in #questions

ArkErrors serialization/deserialization

It does serialize typing schema but what about ArkErrors?

10 replies

Gaming

Programming