Swift contains method entry
Description
This is an attempt to create an initial entry for the .contains() method in swift dictionaries. Hoping to contribute information to the users and learners of swift.
Issue Solved
Closes #5118
Type of Change
- Adding a new entry
Checklist
- [ / ] All writings are my own.
- [ / ] My entry follows the Codecademy Docs style guide.
- [ / ] My changes generate no new warnings.
- [ / ] I have performed a self-review of my own writing and code.
- [ / ] I have checked my entry and corrected any misspellings.
- [ / ] I have made corresponding changes to the documentation if needed.
- [ / ] I have confirmed my changes are not being pushed from my forked
mainbranch. - [ / ] I have confirmed that I'm pushing from a new branch named after the changes I'm making.
- [ / ] I have linked any issues that are relevant to this PR in the
Issues Solvedsection.
trying my luck now, thanks
@SaviDahegaonkar
thank you
Hi @arisdelacruz I see that there are some conflicts please resolve them
@cigar-galaxy82
What's the best way to do this? Thanks
Hi @arisdelacruz I think you created this PR on an old branch that was used for a different PR related to Pytorch while creating this PR you deleted old files and that is why there was a conflict
Hi @arisdelacruz I think you created this PR on an old branch that was used for a different PR related to Pytorch while creating this PR you deleted old files and that is why there was a conflict
@cigar-galaxy82 Do I need to create a fresh entry?
Hi @arisdelacruz raise a new PR with the current file
Hi @arisdelacruz raise a new PR with the current file
ayt! Thanks.
@cigar-galaxy82
I think I'm hitting the wrong buttons. Do I need something like VS Code here? Thanks
@mamtawardhani @cigar-galaxy82
Hi guys. I further checked the conflict connected with the swift contains entry using VS Code. The conflicting entry (well, at least in connection to what I'm trying to push) was one made by a certain Iker Velez. Uhm, will this mean that I'm gonna overwrite the existing one? Please advise further. Thanks much
Hey @Sriparno08 @dakshdeepHERE, I just checked - an entry for this term already exists. I guess there must have been some misunderstanding raising the issue related to this PR, as it already exists in docs.
Could you help me with what can be done here? Should I proceed with this PR or close it? (Also, the format issue is not getting fixed for this)
Yeah @mamtawardhani, there has been a misunderstanding in terms of assigning an author to the corresponding issue. Though @arisdelacruz is assigned to it, this issue has already been completed via this PR by another author. So, I think we need to close this PR unfortunately.
Yeah @mamtawardhani, there has been a misunderstanding in terms of assigning an author to the corresponding issue. Though @arisdelacruz is assigned to it, this issue has already been completed via this PR by another author. So, I think we need to close this PR unfortunately.
Got it, thank you! @arisdelacruz We'll have to close this PR as this term already exists in the docs. Thank you for your cooperation, and sorry for the inconvenience caused!
@mamtawardhani @Sriparno08
No prob, guys. All good.
Thanks