Skip to content

Refactor one thing #45

@arc-teaching

Description

@arc-teaching

Continuing with the example you reviewed before and the discussion you had (issues #42, #43, #44). Let's implement at least one improvement.

  1. First, take around 5 minutes to plan your changes.
  2. Once that is done, start making changes according to your plan.

To get the files on your computer and push them back, remember to:

  1. Fork the repository
  2. Clone your fork
  3. (create branch, make changes, commit...)
  4. Push back to your fork

You can submit a Pull Request for the original repository when you have made some change.

  • You don't have to wait until they're all done!
  • Target the main branch of the original repository
  • Indicate the example you have worked on in the title of the PR, e.g., "Boids: rename variables"
  • Link your PR to this issue adding Answers UCL-COMP0233-25-26/RSE-Classwork#45
  • If you have more time, add more commits to your branch so they are included in the pull request (update the title accordingly if needed)

Metadata

Metadata

Assignees

No one assigned

    Labels

    week09Structure and design

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions