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

Refactor FeatureCrawler code #26

Closed
x97mdr opened this issue Nov 7, 2011 · 0 comments
Closed

Refactor FeatureCrawler code #26

x97mdr opened this issue Nov 7, 2011 · 0 comments
Assignees
Milestone

Comments

@x97mdr
Copy link
Owner

x97mdr commented Nov 7, 2011

The FeatureCrawler generates a tree of FeatureNode objects. I think it would be better to use sub-classes to represent the different type of nodes that one could encounter (Directory, Feature file, Markdown file, etc.) so that we can add support for other types of files if it becomes necessary. Would also clean up some of the feature crawling code.

@ghost ghost assigned x97mdr Nov 7, 2011
x97mdr pushed a commit that referenced this issue Nov 14, 2011
…ent the different types of files processed, adding ability to easily create other types in the future
x97mdr pushed a commit that referenced this issue Nov 14, 2011
@x97mdr x97mdr closed this as completed Nov 14, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant