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

docs(CONTRIBUTING): add GitHub Issue and PR template #1432

Closed

Conversation

staltz
Copy link
Member

@staltz staltz commented Mar 7, 2016

Also about checklist to include new operators

Fixes issues #1355 and #1429

@@ -0,0 +1,21 @@
<!--
Copy link
Member

Choose a reason for hiding this comment

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

is this comment appears up in template? view markdown in PR shows only non commented parts.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup it appears. I saw it in Typescript repo's issue template.

@todoubaba
Copy link

I prefer not use the Issue and PR template, look at the angular2's new issures, it's annoying and not provide clearer intents.

@kwonoj
Copy link
Member

kwonoj commented Mar 7, 2016

I'm still in favor of (at least trying) template to see if this can help anyone who want to contribute can leverage it. After rolling this out and notice if this confuses people, can be easily taken out.


Before you continue, consider the following:

If you have a "How do I do ...?" question, it is better for you and for us that this question is placed in [StackOverflow](http://stackoverflow.com/questions/tagged/rxjs) or some chat channel. This way, you are making it easier for others to learn from your experiences too.
Copy link
Member

Choose a reason for hiding this comment

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

I think StackOverflow actually has an rxjs5 tag.

Copy link
Member

Choose a reason for hiding this comment

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

I'd like to reword this section, honestly. (Sorry, haha)

QUESTIONS: Please direct questions to [StackOverflow](http://stackoverflow.com/questions/tagged/rxjs), our maintainers and the larger community actively answer questions there, and it's a much better format for Q&A. It's also more likely to help others with similar questions.

@staltz staltz force-pushed the operator-contribution-guideline branch from 0214964 to 2fbac1d Compare March 7, 2016 19:49
@staltz
Copy link
Member Author

staltz commented Mar 7, 2016

@kwonoj can you help explain what a Type Definition test is and where to find a good example?

@staltz
Copy link
Member Author

staltz commented Mar 7, 2016

PS @Blesh I updated the PR

Also about checklist to include new operators

Fixes issues ReactiveX#1355 and ReactiveX#1429
@staltz staltz force-pushed the operator-contribution-guideline branch from 2fbac1d to 9fbfb5b Compare March 7, 2016 19:50
@kwonoj
Copy link
Member

kwonoj commented Mar 7, 2016

Type definition test can be found at opened PR #1189 / #1414 (it's not checked in yet) .

Basically it tries to test interface of operators to conform

  • operator input signature accepts parameter as expected
  • operator chain, or subscription correctly delivers context of value type <T>

@kwonoj
Copy link
Member

kwonoj commented Mar 8, 2016

Change looks good to me, explanation regarding type definition test can be added later in detail once PR's checked in.

@kwonoj
Copy link
Member

kwonoj commented Mar 9, 2016

Merged with e92a7b3, thanks @staltz

@kwonoj kwonoj closed this Mar 9, 2016
@staltz staltz deleted the operator-contribution-guideline branch March 9, 2016 14:48
@staltz
Copy link
Member Author

staltz commented Mar 9, 2016

Change looks good to me, explanation regarding type definition test can be added later in detail once PR's checked in.

Yeah you can do that since you understand better about those tests.

@lock
Copy link

lock bot commented Jun 7, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants