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

Consider using custom property treemaType instead of overloading format #35

Open
sderickson opened this issue May 28, 2014 · 0 comments
Milestone

Comments

@sderickson
Copy link
Contributor

To signal to Treema what custom node is what type, it uses type and format to check for entries that match. Perhaps instead of relying on these, we should use a custom schema property to signal to Treema which strategy to use. This way it's more explicit what we're doing.

@sderickson sderickson added this to the Version 0.2 milestone May 28, 2014
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

No branches or pull requests

1 participant