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

Don't complain inside quotes #4

Closed
why-jay opened this issue Sep 15, 2015 · 14 comments
Closed

Don't complain inside quotes #4

why-jay opened this issue Sep 15, 2015 · 14 comments

Comments

@why-jay
Copy link
Owner

why-jay commented Sep 15, 2015

No description provided.

@why-jay
Copy link
Owner Author

why-jay commented Jan 9, 2016

I'm no longer sure why this should be the case.

@why-jay why-jay closed this as completed Jan 9, 2016
@why-jay
Copy link
Owner Author

why-jay commented Jan 9, 2016

Oh, I think this is talking about ."

@why-jay why-jay reopened this Jan 9, 2016
@why-jay why-jay closed this as completed in dd51a6e Jan 9, 2016
@dirk-thomas
Copy link
Contributor

I am not sure if the new behavior makes sense. In the following sentence I don't think it makes sense to require a newline:

Alice asked me "how was your holiday?" on the telephone.

I interpreted the label of the ticket exactly the other way around. Before requiring a space following the dot / question mark it was warning about the missing newline which I though was not desired. But with the new behavior which needs a space afterwards I though the desired goal was already achieved - to not force a newline here.

@why-jay
Copy link
Owner Author

why-jay commented Jan 10, 2016

Hmmmmm...... Your point is valid. I might just revoke the behavior.

@wooorm thoughts?

I'm sure there are cases where a newline after ." (or whatever) would be desired, but can't think of one right now. If so, I think it'll come down to pros and cons of the new behavior within the boundaries of not being tied to any language.

Should I revoke this behavior? Feedback welcome.

@why-jay why-jay reopened this Jan 10, 2016
@wooorm
Copy link

wooorm commented Jan 10, 2016

Maybe a better way to detect a sentence break is also by checking whether after the terminal-marker, there’s a upper-cases letter. Thus, holiday?" on is not a sentence break by holiday?" On is.

@dirk-thomas
Copy link
Contributor

I don't think that the case of the following letter can be used for that. E.g. any name would be upper case but doesn't imply a new sentence.

I would rather avoid any false positives even if that means there are some false negatives left.

@why-jay
Copy link
Owner Author

why-jay commented Jan 11, 2016

I agree with @dirk-thomas. If one wants to add a newline, we should allow the freedom to do so. But we should not force it. I'm going to merge @dirk-thomas's PR #21

@why-jay why-jay closed this as completed Jan 11, 2016
@why-jay
Copy link
Owner Author

why-jay commented Jan 11, 2016

Do you guys think this is a breaking change? Should I update the major version?

@wooorm
Copy link

wooorm commented Jan 11, 2016

Yup, go for it :)

@dirk-thomas
Copy link
Contributor

The change was inserted just two days ago. I would just release a minor (or even patch).

Anyway I am looking forward to use the upcoming version for our stuff 😉 Thanks.

@wooorm
Copy link

wooorm commented Jan 11, 2016

I normally wouldn’t care much either, the number of users is quite low and the chances of breaking builds is small, but still, they’re definitely breaking, so if you want to be more correct, go for a major!

@why-jay
Copy link
Owner Author

why-jay commented Jan 11, 2016

I'll go for a major bump. Thanks for the input.

@dirk-thomas
Copy link
Contributor

Are you going to release soon so that users can use this or are you waiting for other changes?

@why-jay
Copy link
Owner Author

why-jay commented Jan 12, 2016

I'll release it today.

On Tuesday, January 12, 2016, Dirk Thomas notifications@github.com wrote:

Are you going to release soon so that users can use this or are you
waiting for other changes?


Reply to this email directly or view it on GitHub
#4 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants