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
samples for CharSequence.toContain... in api-infix #1543
Comments
@Nikos-Tsiougranas write a comment if you want to tackle it and I'll assign it to you |
May I work on this? [and potentially few other related ones] |
Sure, I suggest you transform one method in CharSequenceToContainCheckerSamples and then create a draft PR so that I can already give you feedback before you continue with the rest. (please don't work on other issues in parallel, once this one is complete, we can find you another issue you can work on -- I have created multiple similar issues because hacktoberfest starts soon and there are always a lot of newcomers to open source development and I would like to give them the chance to work on something easy manageable) |
@robstoll ah ok, created a draft PR for CharSequenceToContainCheckerSamples, let me know how it looks. I will do maybe another one or so and leave the rest. |
Looks all good 👍 |
@robstoll sounds good will wrap this one up soon and then see if I can tackle some other less easy issues from before. |
@rohitverma007 are you still working on this? |
Platform (all, jvm, js): all
Extension (none, kotlin 1.3): none
Code related feature
we already have corresponding samples in api-fluent, the goal is to copy the following examples to api-infix and transform them to the infix style:
TODOs:
@sample
(see api-fluent for examples)Your first contribution?
I'll work on this
if you would like to take this issue over.This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
(Invite yourself in case you do not have an account yet).
The text was updated successfully, but these errors were encountered: