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

Allow debugging unminified source code. Update README.md #69

Merged
merged 1 commit into from
Mar 27, 2014

Conversation

kate2753
Copy link
Contributor

There is no clearly defined and documented way to debug unminified dust-helpers.js code. Adding this ability with grunt testClient task. It is the same approach as in main dust repo (although testClient task uses unminified source file there).

Additionally coverage report generated by jasmine task was based on minified dust-helper.js file. It was hard to tell which lines were covered, since all of it was just one line. Moved out coverage task as a separate task and made it generate report based on unminified source code.

Added grunt watch task to be in line with main dust project and just because it's handy :)

Also update README.md to provide instructions on how all of these tasks should be used.

With these updates travis build will run unit tests against minified dust helpers code in Phantom, Node and Rhino. It will also run coverage report against unminified source code. If coverage thresholds are not met, build will fail.

grunt.registerTask('releasePatch', ['bump-only:patch', 'buildRelease', 'shell:gitAddArchive', 'bump-commit']);
grunt.registerTask('releaseMinor', ['bump-only:minor', 'buildRelease', 'shell:gitAddArchive', 'bump-commit']);

//default task - full test
grunt.registerTask('default', ['test']);
grunt.registerTask('default', ['test']);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stray tab?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might seem so :), but no, this is intentional. All of the task arrays are tab aligned, so it's easier to glance through them.

Take a look at the "Grunt tasks aliases" section at the bottom of the gruntfile, and you'll see what I'm talking about.

@jimmyhchan
Copy link
Contributor

Looks good.

prashn64 added a commit that referenced this pull request Mar 27, 2014
Allow debugging unminified source code. Update README.md to explain these changes.
@prashn64 prashn64 merged commit 27fe228 into LinkedInAttic:master Mar 27, 2014
@prashn64
Copy link
Contributor

Thanks!

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 this pull request may close these issues.

3 participants