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

Documentation doesn't use best practices for writing your own externalizers #117

Closed
jamadden opened this issue Jul 23, 2021 · 0 comments · Fixed by #120
Closed

Documentation doesn't use best practices for writing your own externalizers #117

jamadden opened this issue Jul 23, 2021 · 0 comments · Fixed by #120

Comments

@jamadden
Copy link
Member

It should at least note that the best practice is to either extend one of the existing externalizaers (not start from scratch) or to at least begin with to_standard_external_dictionary

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