Using new cosmwasm_schema

public-awesome / cw-nfts

Examples and helpers to build NFT contracts on CosmWasm

Apache License 2.0

185 stars 181 forks source link

Using new cosmwasm_schema #102

Closed peara closed 1 year ago

peara commented 1 year ago

I try to implement what's in #81. Remaining issues:

In cw2981-royalites, QueryMsg<Cw2981QueryMsg> is used. As in cw721-base generates an empty response for Extension, there is no response generated for Cw2981QueryMsg. I haven't found a solution for this.
In cw721-non-transferable, most of QueryMsg enums are redefined. I want a more robust solution than copy lines from cw721-base.

peara commented 1 year ago

@shanev @larry0x Can you help me check why circle ci didn't run?

webmaster128 commented 1 year ago

For some strange reason, no CircleCI build is started. I don't know why. I'll set a reminder to check again tomorrow.

webmaster128 commented 1 year ago

We are getting builds now :)

peara commented 1 year ago

It was because I asked Circle ci to check my fork... really sad!

webmaster128 commented 1 year ago

Strange because fork builds are enabled and they worked for other PRs here before. I see the build in https://app.circleci.com/pipelines/github/CosmWasm/cw-nfts now.

peara commented 1 year ago

Strange because fork builds are enabled and they worked for other PRs here before. I see the build in https://app.circleci.com/pipelines/github/CosmWasm/cw-nfts now.

Before submitting this PR, I enabled CircleCI on my own fork and that blocked it from running it here.