phineasla
phineasla
https://github.com/PolyMeilex/node-myanimelist/blob/567d96be09c476a6460b453fa52524cafec4e3a1/src/methods/jikan4/types.ts#L680 The ```entry``` property is an object, not an array: https://api.jikan.moe/v4/anime/43608/recommendations Example: ```JSON { "data": [ { "entry": { "mal_id": 38101, "url": "https://myanimelist.net/anime/38101/5-toubun_no_Hanayome", "images": { "jpg": { "image_url": "https://cdn.myanimelist.net/images/anime/1819/97947.jpg?s=63766d471cbb06b0bc8d4c81d5fc98fe", "small_image_url":...
I find that overriding `router.render` is cumbersome, so I changed it to using express router, this will keep the lowdb operations while allowing custom responses. I don't know if anyone...
``` yarn run v1.22.10 $ mongodb-runner start [Error: EPERM: operation not permitted, symlink 'C:\Users\lucass\.mongodb\versions\mongodb-5.0.1-windows-64' -> 'C:\Users\lucass\.mongodb\versions\mongodb-current'] { errno: -4048, code: 'EPERM', syscall: 'symlink', path: 'C:\\Users\\lucass\\.mongodb\\versions\\mongodb-5.0.1-windows-64', dest: 'C:\\Users\\lucass\\.mongodb\\versions\\mongodb-current' } ```
Specta 2.0.0 removed `recordFailureWithDescription:inFile:atLine:expected:` in favor of `recordIssue:`, causing "unrecognized selector sent to instance" error when an expectation fail: ``` -[FooSpec _recordUnexpectedFailureWithDescription:exception:]: unrecognized selector sent to instance 0x106709ca0 (NSInvalidArgumentException) ```...
This solves the incompatibility issue with Specta 2.0.0 replaced `recordFailureWithDescription:inFile:atLine:expected:` with `recordIssue:`