Codecademy / docs

Codecademy Docs is a collection of information for all things code. 📕

Home Page:https://www.codecademy.com/resources/docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Term Entry] Dart List .forEach()

christian-dinh opened this issue · comments

Reason/inspiration (optional)

We would like a new term entry under Dart List for the Dart List .forEach() method.
Provide the entry in a markdown file under docs/content/dart/concept/list/terms/forEach/forEach.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

Hello! I would like to create an entry on this subject.

I'm a codecademy student, currently enrolled in the Git & GitHub course. I've reached the part of the syllabus where I'm required to contribute to the documentation repository as part of the project.

Please let me know when the issue is assigned for development.

Thank you :)

@aeonclouzeau You're assigned!! 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.

Is this your first contribution to Codecademy Docs? If so, we're curious to know how you found out about contributing to Docs.

🌸 Thanks for closing this Issue!
Please head over to the Docs Forum if you have any questions about Docs, or reply to the thread on Possible Content Discussion to share ideas and collaborate with other contributors, maintainers, or super users to determine good future issues that will help expand Docs!