rawAttributes deprecated but still used in Typescript docs (docs) (v7)

Open
#352 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
documentation

Research direction

Open the linked v7 TypeScript documentation page and search its examples for rawAttributes. Update the affected examples to use getAttributes, then review the page to confirm no deprecated rawAttributes usage remains.

Written by the indexing model from the issue text.

Description

Issue Creation Checklist

  • [x ] I understand that my issue will be automatically closed if I don't fill in the requested information
  • [ x] I have read the contribution guidelines

Bug Description

I noticed that the documentation for v7 still uses the static rawAttributes method instead of getAttributes. rawAttributes is deprecated.

Reproducible Example

as of alpha-19

Here is the link to the SSCCE for this issue:

https://sequelize.org/docs/v7/other-topics/typescript/

What do you expect to happen?

The examples should use non deprecated code.

What is actually happening?

It uses deprecated code

Environment
  • Sequelize version: v7.0.0-alpha.19
  • Node.js version: v16
  • If TypeScript related: TypeScript version: v4.8
  • Database & Version: mysql 5.7
  • Connector library & Version: msql2

Would you be willing to resolve this issue by submitting a Pull Request?

  • Yes, I have the time and I know how to start.
  • Yes, I have the time but I will need guidance.
  • No, I don't have the time, but my company or I are supporting Sequelize through donations on OpenCollective.
  • No, I don't have the time, and I understand that I will need to wait until someone from the community or maintainers is interested in resolving my issue.

Indicate your interest in the resolution of this issue by adding the 👍 reaction. Comments such as "+1" will be removed.

Dominant language
HTML
Stars
30
Forks
170
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sequelize/website

All issues in sequelize/website

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.