Rik Smale

Hi all! I think that we can accept PRs for this but it's not a priority for the current maintainers to implement this ourselves. So feel free to make a...

Just to spare the people looking into this a click; this relates to the v6 API reference which is still built with esdoc.

I looked a bit into this and this is probably because the file was already migrated to TypeScript in v6 and therefore not picked up by esdoc. We're tracking this...

I can reproduce this by the following failing test in `test/unit/sql/where.test.ts`; ```ts testSql({ 'jsonAttr.edges[*].nested': { attribute: 'value', }, }, { mysql: `json_unquote(json_extract(\`jsonAttr\`,'$.\\"edges\\"[*].\\"nested\\".\\"attribute\\"')) = 'value'`, }); ``` According to the MySQL...

@Vigneshwaran16 feel free to open a PR for this!

Yeah, that's our most flaky test. Don't worry about it

Feel free to broaden the scope of this PR and fix more typings here. If possible do limit it to typings of model.js in this PR

> That option does not exist for SQLite. `dialectOptions` are passed to the dialect library as-is, and [sqlite3](https://www.npmjs.com/package/sqlite3) does not have any such option Not sure why this wasn't closed...

There's some failing integration tests. And apparently postgres does a much better stacktrace than the other dialects, that might be something to look into in the future

I've looked at this PR. The `databaseVersion` is not required anymore and with our [TypeDoc](https://sequelize.org/api/v7/classes/sequelize#createSchema) it is clear which options are supported. I think therefore we can close this issue....