Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve and standardize parsing API #364

Open
carreter opened this issue Sep 23, 2023 · 1 comment
Open

Improve and standardize parsing API #364

carreter opened this issue Sep 23, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request hard A major or complex undertaking high priority High priority - something is broken or missing that is critical for users or developers. stale ux Issues with user experience of using the package
Milestone

Comments

@carreter
Copy link
Collaborator

We need to standardize/clean up the API for the parsers.

@carreter carreter added enhancement New feature or request ux Issues with user experience of using the package high priority High priority - something is broken or missing that is critical for users or developers. hard A major or complex undertaking labels Sep 23, 2023
@carreter carreter added this to the v1.0 milestone Sep 23, 2023
@carreter carreter mentioned this issue Sep 23, 2023
@carreter carreter moved this to In Progress in poly development roadmap Sep 23, 2023
@carreter carreter changed the title Improve and standardizing parsing API Improve and standardize parsing API Sep 23, 2023
Copy link

This issue has had no activity in the past 2 months. Marking as stale.

@github-actions github-actions bot added the stale label Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hard A major or complex undertaking high priority High priority - something is broken or missing that is critical for users or developers. stale ux Issues with user experience of using the package
Projects
None yet
Development

No branches or pull requests

2 participants