Bjarte S. Karlsen

Sorry for not following up, but I left my old job back in december and no longer work on this.

Can we consider overflow or flow-js-testing for tests here? Both a very much more readable then these tests that contains alot of boilerplate.

Today I removed the "B imports C" part in my code and then I am below the limit again. C in my case here is FIND and that contract is...

Also when I ran the default example the finisher panics but it just makes the job run endlessly, should the hookFunc return an error?

One issue is that in the example code or in the ddl there is no sql for the finished logs table.

Ok, well if you add the finished job table to the ddl it will work better imho.

I almost think that when default implementation is in we should make nft 1.1 that is bc with NFT with just default impl. It is going to make life so...

Do we have an ETA for when default implementations will be added to cadence on testnet/mainnet. Default adding of getViews/resolveViews to NFT resource would also be lovely.

getViews/resolveViews are not on the collection, they are on the resource are they not? if we specify that the nft interface needs it and default implement it as empty it...

I think so too, but after default implementations are here, we can just try and see that it works.