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

process ready items always even if others fail #1229

Merged
merged 2 commits into from
Jun 30, 2017
Merged

process ready items always even if others fail #1229

merged 2 commits into from
Jun 30, 2017

Conversation

endevea
Copy link
Contributor

@endevea endevea commented Jun 22, 2017

Fixes issue #1218.

Copy link
Member

@iangilman iangilman left a comment

Choose a reason for hiding this comment

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

Very nice elegant solution!

Just one little change and it should be ready to land :)

.eslintrc.json Outdated
@@ -10,7 +10,7 @@
],
"linebreak-style": [
"error",
"unix"
"windows"
Copy link
Member

Choose a reason for hiding this comment

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

This needs to stay "unix". Is your editor not respecting the linebreak style that's already in the files?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

eslint kept complaining. I work on windows. Will set it back to Unix.

@endevea
Copy link
Contributor Author

endevea commented Jun 30, 2017

is there something else I should do now? still a noob

@iangilman iangilman merged commit d6bf2db into openseadragon:master Jun 30, 2017
@iangilman
Copy link
Member

@endevea Nope... just didn't have a chance to get to it earlier. Looking good :) Thank you again for making this fix!

Regarding the eslint thing, you should be able to set your text editor to respect the line break style that's already in the files, regardless of what OS you're on. Which text editor are you using, out of curiosity?

@endevea
Copy link
Contributor Author

endevea commented Jul 3, 2017

VS code is the text editor. However, eslint complained about CRLF/LF in all files when building even before any editing was done. It must be a git setting of mine.

@iangilman
Copy link
Member

Interesting... yes, sounds like git is somehow converting the line endings!

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.

2 participants