-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature/better project page #138
Conversation
…le for use on the project page.
… start handling them and communicating them to the user.
…h cannot be parsed.
This is separate from the file tree work. |
Found some issues, don't merge. |
Fixed... |
… promises for the file contents on the file object.
…ile list. Use a modified version of the file-tree module with a bug fix until the pull request with the fix is accepted.
…file tree. Add a polyfill file.
…irectory. Render that.
Okay, re-opening with basic file tree work done. Files are arranged by directory clicking the directory name will toggle those files. |
…ts after reopening it.
@sponte Ready for review, although it will probably need us both. We have the data to do whatever we want with the UI but I'd suggest this is good enough for now. |
@@ -261,7 +262,7 @@ function getAllFiles(tree) { | |||
return _getAllFiles(tree) | |||
.then(function (files) { | |||
return files.filter(function (f) { | |||
return /\.(feature|md)/.test(f); | |||
return (appConfig.regex.fileOfInterest).test(f); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move file filtering into project.js rather at low level inside please?
Redesign the project page. See individual commit messages.
Also note a bug in the update functionality, reported in #137 .