Skip to content

Add caveats to README #42

@ramonechen

Description

@ramonechen

This completely slipped my mind when first writing the README, but I think it's important to have a section that explains all of the caveats of the scraper project. This can include but is not limited to:

  • Ever-changing data on the SIS platform
  • Potential future incompatibilities with new data
  • Assumptions made in order for the scraper to work
  • Precautions taken to maximize flexibility of the scraper

This way, users would be able to take a guess as to what may be wrong in the case that the scraper breaks in the future.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions