chore: update @fadroma/schema to 1.1.0

[egasimus]

This adds a footer to generated docs which contains:

• Name of schema file used to generate schema
• First 16 characters of SHA256 hash of source schema file
• Link to https://www.npmjs.com/package/@fadroma/schema and version used
• Link to https://fadroma.tech/

I hope the latter two are acceptable. We're trying to raise awareness of our toolkit's existence, and would be happy to collaborate more closely with your team in the future.

[codecov]

Codecov Report

Merging #342 (c80889d) into main (bd3470a) will increase coverage by 0.21%.
Report is 37 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #342      +/-   ##
==========================================
+ Coverage   98.04%   98.25%   +0.21%     
==========================================
  Files          41       42       +1     
  Lines        8861     9766     +905     
==========================================
+ Hits         8688     9596     +908     
+ Misses        173      170       -3     

see 8 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

📢 Have feedback on the report? Share it here.

[antho31]

Hello @egasimus

The following is all about suggestions, and fully open to discussions.

We understand your awareness concerns, but we are looking to work in another way to value/reward contributors.

We better prefer to grant fadroma's use as a Builder program's open contribution (the 4th challenge of "Invoke the power of Dagda" part, eligible up to 100 000 $KNOW).
And even for deeper collaboration, what about a similar package as well as there is with Secret, for OKP4? We saw OKP4 mentioned in the Medium article :)

[egasimus]

Hi @antho31!

Adding a reference to the inputs and generating tool in generated documentation is a normal thing that some doc generators do and some don't, e.g.

TypeDoc:

Sphinx/Read the Docs:

Though I do notice that neither Docusaurus nor mdBook elect to do it 🤷

Either way, this is a general contribution in accordance with established FOSS practices. It effectively costs you nothing to lend us this tiny bit of publiciity - but I'm willing to remove the links from axone-protocol/docs#276 if this will expedite the publication of the fixed docs.

I'm happy to hear that this contribution also fits the criteria for Dagda (if I understand you correctly). We actually have something else in mind for the builders program - and yes, it includes adding a full OKP4 client to Fadroma :-)

We planned to publish that by Aug 30, then hit a snag with a lot of the foundational libraries (@cosmjs/stargate and protobuf.js among others) not being natively ESM-compatible. So I'm currently working on a comprehensive solution for all that (which I hope will benefit not only OKP4, but CosmWasm and the JS ecosystem in general).

If all goes well, we plan to release a beta version of our graphical chain explorer with OKP4 support by Sep 30. Please email us at hello at fadroma dot tech and let's have a conversation about how to best move this forward - imho GitHub Issues aren't the best medium for strategic discussion.

[antho31]

Alright, just sent you a mail :)

[bdeneux]

Thanks 🙏 !
By changing version, the new documentation generated differ and linter doesn't accept if you don't commit this new documentation.
If you can please commit the new generated documentation so that it can be up to date on the docs repository 😇:

cargo make docs-generate

[egasimus]

Done! 😄

[amimart]

Thx! 🙏

[ccamel]

👏 Thanks

[bdeneux]

Thanks 🙏!