Tom Quist

Yes, that's possible. You can do this: ```yaml sources: - path: Sources excludes: - Sources/Resources - path: Sources/Resources type: folder ```

The problem is that the system framework WatchKit.framework in `/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/Frameworks/WatchKit.framework` is also loaded and `NSClassFromString` returns the real WatchKit class instead of the shadow class. The real implementation returns `nil`...

We're also running into that issue. Is this something that's being worked on?

A workaround is to introduce another subquery like this: ```typescript await Foo.findAll({subQuery: true, order: sequelize.literal(`(SELECT tmp.my_name FROM "Foos" AS tmp WHERE tmp.id = "Foo".id)`)}) ``` But this makes the query...

Please note that I'm not expecting a literal to be modified. The alias of the attribute is not a literal and Sequelize IS modifying it already (e.g. it converts the...

Exactly! Sorry, my issue description could've been a bit more to the point.

Thanks for the heads-up, @evanrittenhouse! Unfortunately, I can't easily test the fix on our project since we're still on Sequelize 6 and can't easily migrate to 7 just for this...

Unfortunately, we ran into an issue with this change. It seems that when using `subQuery: true` the order direction is only applied to the outer query but not to the...

I was digging a bit deeper into this and found that jest reads the message from the error's `stack` property. However, since Sequelize injects the stack trace from a dummy...

We're working around this now using this function: ```typescript function monkeyPatchSequelizeErrorsForJest(instance: Sequelize) { if (typeof jest === "undefined") { return; } const origQueryFunc = instance.query; instance.query = function (this: Sequelize,...