mikeymike/php-workshop

PHP Workshop Application

php-workshop's Issues

Run PHP with E_ALL & display_errors

TODO

• Initial console menu (with Climate ?)
• Lesson / Task interface
• Lesson / Task validators (default being a simple expects)
• Lesson / Task page, output details
• Lesson / Task runner
• All the tests
• Move SyntaxHighlighter to separate package
• Finish tests for SyntaxHighlighter
• Docs for SyntaxHighlighter
• Pin php-workshop to php-parser 2.x@beta
• Fix tests (Update usages of php-parser to 2.x)
• Add CLI command parsing (verify, run, help) etc
• Fix mark-down URLS's (don't wrap in curly braces)
• Build output page for task
• Replace variables in markdown files, like {appname}
• Use Terminal object in markdown-render for stuff like screen width

Check code for errors and warning

A users solution may trigger errors and warnings. This would be contained in the output and would obviously fail the StdOutCheck. However, could we provide more meaningful feedback?

PhpErrorCheck

• We could grep the output for PHP Notice: and PHP Warning. This seems a bit flaky as that could be valid output.
• We could lint the file first, check if it's valid PHP code, then parse the file and add in some code, like an error-handler which would exit with a non-zero error code.

Support Windows 100%

We should add http://www.appveyor.com/ as a CI service.