Separate ToSchema from PAB usage about plutus-apps HOT 4 CLOSED

Thanks for the issue!

Yeah, the architecture has changed a bit and ToSchema should be separated from the PAB.

But it shouldn't be a blocker for you now. HasDefinitions instance is the only place where ToSchema is required and you can ignore it by returning an empty list:

instance HasDefinitions MarketplaceContracts where
   ...
   getSchema = []
   ...

from plutus-apps.

It does not solve the problem, because at some point it requires for all inputs (it acts as redeemer) to have that instance in the schema. So it forces to have ToSchema instance for all inputs. I'm not sure where it happens, but it's better to remove that then.

from plutus-apps.

It does not solve the problem, because at some point it requires for all inputs (it acts as redeemer) to have that instance in the schema

Can you please share an example? Because I don't see it yet.

from plutus-apps.

Closing as solved in #212.

from plutus-apps.