Skip to content

QUESTION: Should I write my own tokenizer for GenericSegments? #4

@cole-maxwell1

Description

@cole-maxwell1

Hi,

I am new to the X12 EDI format, and I have a question about the intended use of this package. Is your intent to have people write a tokenizer that fits their specific use case? For example, I would like to use this package to deserialize an 834 Benefit Enrollment and
Maintenance
file into custom rust structs. In the crate, the structs like InterchangeControl have a function parse_from_tokens(). Would you recommend that I follow that approach?

If you are willing to write it, having an example guide of how people might write something to process GenericSegment structs into their own structs would be very helpful. It doesn't necessarily need to be an 834 doc. For example, Golang's omniparser library has a nice guide where they use the UPS 240/214 as an example. But that's no fun because it's Golang, not Rust! Let me know if there's any way I could help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions