Alyx
Alyx
Can you post the TS error you're having?
@kamronbatman very late with my reply but yes, we're changing how models are typed. This is a change from upstream Sequelize. It's very unfortunate that it lead to an error...
I can confirm that this is a bug in Sequelize, not Sequelize-Typescript. I've reopened your issue @goalia
We have recently fixed this in Sequelize 7, but it hasn't been backported to Sequelize 6 yet https://github.com/sequelize/sequelize/pull/14022
Is this still an issue? It should have been fixed in Sequelize 6.7.0 by https://github.com/sequelize/sequelize/pull/13510
Setting their queueId to null should do it: ```typescript await ticket.update({ queueId: null }); ```
Thanks for the response. I'll try to explain my issue with graphCache's relayPagination a little bit better :) My issue is an interaction between the `cache-and-network` policy and `relayPagination`, exacerbated...
Invalidating each query individually would work for a force refresh. One of the things I like about this RFC that I'm not sure can currently be done is that I...
If anyone else is encountering the same bug, my current workaround is to go back to using to `json-loader`: ```javascript module: { rules: [{ test: /\.json$/i, type: 'javascript/auto', loader: 'json-loader',...
Any update on this? Support for brotli grows but this prevents us from using it plus gzip as a fallback because gzip is always returned by `preferredEncodings`.