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

Fixed the tooltip in Strikethrough and added comments to readme #597

Closed
wants to merge 12 commits into from

Conversation

Percussionista
Copy link
Contributor

Added the tooltiptext to the strikethrough tool and added some comments to the readme to give a better idea where to look when needing to customize the toolbar. This section could stand to be fleshed out by someone more knowledgeable than me.

I also fixed the wordcount action function to not freak out when markup is added within a word. I added some unit tests to ensure that the counts are still correct.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f81f7ca on Percussionista:master into cb1c7ce on fraywing:master.

@Percussionista
Copy link
Contributor Author

The Travis build is failing due to not having 100% coverage, which is odd since I actually added another test. Any ideas?

@SimeonC
Copy link
Collaborator

SimeonC commented Mar 26, 2015

It says branches, which means if statements - I'd hazard it's this line: https://github.com/fraywing/textAngular/pull/597/files#diff-cbd86781c5c78226e7a486a23a97a0e2R663.

Basically the right side of the || doesn't get tested - i.e. no content. If you want you can just add an coverage ignore else for that line.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 7372c19 on Percussionista:master into f2959fe on fraywing:master.

@Percussionista
Copy link
Contributor Author

Finally! Thanks, SimeonC.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 6e83448 on Percussionista:master into f2959fe on fraywing:master.

@Percussionista
Copy link
Contributor Author

One of the changes I made in this set of pull requests was to the readme file. I added a blurb about customizing the toolbar, which I needed to do for my use case. It took forever to figure out what I was doing and I ended up reading the comments in the demo to try to piece together how to do it. Silly me - I didn't realize the information I needed was mostly in the wiki. If it would speed up my pull request, I am open to removing the changes to the readme file, but I think there should at least be a note pointing users to the wiki for customization information. Thanks!

@SimeonC
Copy link
Collaborator

SimeonC commented Mar 30, 2015

Hey, sorry about the delay - I'm in the middle of changing jobs (2 weeks left!) which doesn't allow me a lot of time for much apart from responding to issues. As soon as I have the time I work through getting PR's merged first then working on some of the outstanding bugs.

@Percussionista
Copy link
Contributor Author

No problem. Congrats and good luck on the new job! You're doing a great job with the project. Thanks!

SimeonC pushed a commit that referenced this pull request Apr 2, 2015
@SimeonC
Copy link
Collaborator

SimeonC commented Apr 2, 2015

This is merged, though I seemed to have stuffed up something and it's not being marked as such.

@SimeonC SimeonC closed this Apr 2, 2015
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.

None yet

3 participants