-
Notifications
You must be signed in to change notification settings - Fork 248
Conversation
Better whitespace handling in toNodeList
Thanks for your contribution! In order for us to be able to accept it, we ask you to sign our CLA (contributor's license agreement). CLA is important for us to be able to avoid legal troubles down the road. For individuals (a simple click-through form): http://code.google.com/legal/individual-cla-v1.0.html |
Alright, signed! Thank you! |
@ofagbemi the commit comment should follow the guidelines from CONTRIBUTING.md and you should also add a unit tests. Thanks. |
@ofagbemi The commit comment should be smthg like 'feat(...): ...' and have |
My apologies. Updated! |
Add whitespace handling to the TestBed’s compile function. Closes #1262. Previously, strings passed with leading or trailing whitespace would be compiled incorrectly. Now, valid HTML with arbitrary whitespace in and surrounding it can be compiled properly.
Thanks, could you squash all the commits now ( |
Add whitespace handling to the TestBed’s compile function. Closes #1262. Previously, strings passed with leading or trailing whitespace would be compiled incorrectly. Now, valid HTML with arbitrary whitespace in and surrounding it can be compiled properly.
Okay, I think that should be it. Let me know if I messed up anywhere! |
When you send a PR you should create a branch on your repo and sending from this branch. To fix this you need to open a new PR (you can not change the source branch of a PR). So:
|
Okay, sent the new PR in #1346. Very sorry for all the confusion. Thanks! |
No problem, thanks for taking the time to update. |
Better whitespace handling in toNodeList