Kinga Cepielik
Kinga Cepielik
• Excluding specific packages from documentation generation Some command-line proposals: Package Exclusion > scarb doc --workspace --exclude macros,macros_tests > scarb doc --workspace --include math,ascii,utils
Repro: ``` pub struct A { pub b: felt252, c: felt252, } ``` will have a signature generated as: ``` pub struct A { pub b: felt252, c: felt252, }...
I'm thinking: - logo - fonts ? - colors
expected example md vs mdx: > # Array > > A collection of elements of the same type contiguous in memory. > > Fully qualified path: [core](./core.md)::[array](./core-array.md)::[Array](./core-array-Array.md) > > pub...
Ideally we want some automated way of using scarb-doc generated mdbook files with mintlify
This can make sense if there is some other usage for the mdx files other than mintify, so the task comes down to finding out such a way of using...
Research how the mdx syntax can be properly supported. [Comment parsing](https://github.com/starkware-libs/cairo/blob/main/crates/cairo-lang-doc/src/parser.rs) for mdx would probably not work with [pulldown_cmark](https://docs.rs/pulldown-cmark/latest/pulldown_cmark/). In that case, what is needed would be either: a separate...
check what isn't documented and should be: - #[doc(hidden)] - doc groups (?) - rules of creating new paragraph (single break vs double)
Example/use-case: from starknet-staking Free functions: unsafe_new_contract_state and Structs: ContractState are generated automatically for a contract. The idea is to hide them from the docs. Note to Kinga 👉 let Noa...