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

Document migration from 0.x to 1.0 #181

Closed
4 tasks done
masklinn opened this issue Feb 6, 2024 · 0 comments · Fixed by #205
Closed
4 tasks done

Document migration from 0.x to 1.0 #181

masklinn opened this issue Feb 6, 2024 · 0 comments · Fixed by #205
Milestone

Comments

@masklinn
Copy link
Contributor

masklinn commented Feb 6, 2024

It's not complicated but still...

Maybe should also explain the increase in depth of the model? Or is it more for #182? Whichever location it is, it should use write more classes as its basis for explanation. Also probably make sure I don't misunderstand and didn't misremember it.

important bits:

  • new API is more lazy by default, global parser is only instantiated when first accessed, not when imported, and that's the moment at which the matchers are instantiated
  • matchers can be made even lazier (by using lazy matchers), though that's probably not a great idea with the basic parser
  • re2 exists
  • most difficult part of the migration is yaml, as the implicit loading was replaced
@masklinn masklinn added this to the 1.0 milestone Feb 6, 2024
masklinn added a commit to masklinn/uap-python that referenced this issue Mar 27, 2024
masklinn added a commit to masklinn/uap-python that referenced this issue Mar 27, 2024
masklinn added a commit that referenced this issue Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant