[Term Entry] Dart List .add()
christian-dinh opened this issue · comments
Reason/inspiration (optional)
We would like a new term entry under Dart List for the Dart List .add() method.
Provide the entry in a markdown file under docs/content/dart/concept/list/terms/add/add.md
The entry should
- Have an introductory paragraph about what the method is and does.
- A syntax section with a pseudo code block with an explanation of it.
- An example showing the method in use.
Please refer to the concept entry templates, content standards, and markdown style guide when working on the PR for this issue.
Entry Type (select all that apply)
New Term for Existing Concept Entry
Code of Conduct
- By submitting this issue, I agree to follow Codecademy Doc's Code of Conduct.
For Maintainers
- Labels added
- Issue is assigned
Hi there, I would like to take on this issue please. I've found this issue through the CodeAcademy "Git and GitHub" modules, as part of my "Contributing to the CodeAcademy Docs Repository" project. Just for further clarity, the request is that the Dart term .add() needs to be added to a directory I need to create - list/terms/add/ where the markdown file will be located?
Hi again, checking in to ask if it would be possible to take on this issue please?
@AnisurRahmanAR You're assigned. You are correct you will need to create list/terms/add/.
In addition to the documents linked in the description, please also look at our Contribution Guide if you haven't already. After creating a PR, the maintainer(s) (with the collaborator label) will add comments/suggestions to address any revisions before approval.
Hi KTom101, I believe I've created the file and followed each of the guides, and I've even pushed to changes to get reviews but I can't make the pull request for some reason.
I keep coming into this image despite having the option to compare and pull request.
I'm not entirely sure what's causing this, and I have tried multiple times to start from the beginning and also searching up solutions. As a beginner, I don't know the work around for this. Sorry for the inconvenience.