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

Prep for 2.0 #2885

Merged
merged 9 commits into from
Nov 25, 2017
Merged

Prep for 2.0 #2885

merged 9 commits into from
Nov 25, 2017

Conversation

dignifiedquire
Copy link
Member

No description provided.

@dignifiedquire
Copy link
Member Author

Need to update the cucumber step defs to fix the tests

@dignifiedquire
Copy link
Member Author

Need to figure out why node 4 and 6 are unhappy

@johnjbarton
Copy link
Contributor

@EzraBrooks
Copy link
Collaborator

EzraBrooks commented Nov 23, 2017

Did you intend to add a Yarn lockfile? The project currently includes neither a yarn.lock nor a package-lock.json. Will 2.0 be taking a stance on which package manager to use?

@dignifiedquire
Copy link
Member Author

@EzraBrooks I have certain opinions on the matter, but I am not yet sure if it makes sense to add them to karma.

@dignifiedquire
Copy link
Member Author

@johnjbarton interesting, I guess this is only a devdependency so it should be fine to stay on the 1.x branch for now

@EzraBrooks
Copy link
Collaborator

Would it be useful for the project to adopt TypeScript's type-checking as part of the lint stage? Just by enabling ts-check on some of the files in the project, there's a lot of ambiguous typing that becomes very obvious. Since you can use the type checking without converting your code to TypeScript, I thought I'd suggest it.

@dignifiedquire
Copy link
Member Author

@EzraBrooks I like the idea, but lets make a separate pr/issue about it.

@dignifiedquire
Copy link
Member Author

This should be ready

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

1 similar comment
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@dignifiedquire dignifiedquire changed the title [WIP] Prep for 2.0 Prep for 2.0 Nov 25, 2017
@dignifiedquire dignifiedquire merged commit 10fac07 into master Nov 25, 2017
@dignifiedquire dignifiedquire deleted the prep-2 branch November 25, 2017 21:45
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.

6 participants