brain-marks
brain-marks copied to clipboard
mikaelacaron
Documentation
Describe the solution you'd like
Document all code with access level internal or higher, except declarations made for protocol conformance or overriding subclasses. This allows developers to understand the intention and function of the public interface of types.
- Basically document all the functions
Additional context This is the conform the the best practices described here
Will do! Sorry I got slammed with take-home assignments and interviews. I'm gonna work start working on the issue this weekend.
Am I adding the above text into the readme? What exactly do you need me to do to clarify.
@jocelyn-boyd No worries! I'm in no hurry, you only have to submit the PR before Oct 31 for it to count for Hacktoberfest. Look at the Coding Style Guidelines in the Contributing file. Documentation is about documenting the code in the project. Some examples are here.
You should document all code where the access level of that code in internal or higher.
This means going into the project and documenting what each class, property, function etc, does and what its purpose is. In Xcode, when you're on the line above a function, class, property, etc. You can click Option + Command + / to automatically make the documentation comment come up, this is the same as using three slashes /// comment here.
How this documentation works can also be found here.
So you are documenting the code itself, not the README.md file.
Apply for one on the Twitter developer site, technically you wouldn't need one for this issue, but if you want to run the project you do need one
I know, I just wanted to run it and see how it works on my computer.
Byw, just comment only on the files in the brain-marks folder? I finally have a chance today to sit down and go through it.
If we want to use DocC: https://www.raywenderlich.com/34919511-docc-tutorial-for-swift-getting-started
I would like to contribute by documenting the functions. Could you please assign it to me ?
@ankurwasnik is assigned this issue right now, but if they don't get to it in the next 3 days, go ahead!
@ankurwasnik let me know if you're still working on this
@helloITdepartment you can always find a different issue to work on :)
@ankurwasnik how's it going working on this issue? Do you have any questions? Do you think you'll complete it by the end of Hacktoberfest?
I think I will complete this before due.
On Tue, Oct 25, 2022 at 7:09 PM Mikaela Caron @.***> wrote:
@ankurwasnik https://github.com/ankurwasnik how's it going working on this issue? Do you have any questions? Do you think you'll complete it by the end of Hacktoberfest?
— Reply to this email directly, view it on GitHub https://github.com/mikaelacaron/brain-marks/issues/80#issuecomment-1290579600, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQIAWF33FMAEC3O4DMNQUTLWE7PJTANCNFSM5F4EK7RQ . You are receiving this because you were mentioned.Message ID: @.***>
do we have to create a new file for all documentation or just add multi-line comments above each function ?
@mikaelacaron can I get this issue I want to contribute please
@dcode333 This project isn't active anymore. I can't maintain it because of changes to the Twitter API
@mikaelacaron I just want to make my first contribution as I have an assignment about it can you help me make my first contribution?? Please even if it's in the documentation...
@dcode333 Does your assignment require that I merge it? If not, you're more than welcome to make a PR, but I won't be merging it
@mikaelacaron The main thing is to get it merged..You can't help me in this regard??
@dcode333 No not for this issue, there's too many changes, and I don't have time to look at it, and I don't know what your timeframe is.
You could try this repo IceCubesApp that is currently being developed. I won't have another open source project to be worked on, until Hacktoberfest this October