forked from paritytech/polkadot-sdk
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix call enum's metadata regression (paritytech#3513)
This fixes an issue introduced in paritytech/substrate#14101, in which I removed the `Call` enum's documentation and replaced it with a link to the `Pallet` struct, but this also removed any docs related to call from the metadata. I tried to add a regression test for this, but it seems to me that this is not possible, given that using `type-info` we only assert in type-ids for `Call`, `Event` and `Error`. I removed some doc comments from a test setup in `frame-support-test` to demonstrate the issue there. @jsdw do you have any comments on this? I also fixed a small issue in the custom html/css of `polkadot-sdk-doc` crate, making sure it does not affect the rust-doc page of all other crates. - [x] Investigate a regression test - [x] prdoc
- Loading branch information
1 parent
27a14e9
commit 2a6486e
Showing
6 changed files
with
157 additions
and
103 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,17 @@ | ||
:root { | ||
--polkadot-pink: #E6007A ; | ||
--polkadot-green: #56F39A ; | ||
--polkadot-lime: #D3FF33 ; | ||
--polkadot-cyan: #00B2FF ; | ||
--polkadot-purple: #552BBF ; | ||
} | ||
|
||
body > nav.sidebar > div.sidebar-crate > a > img { | ||
/* logo width, given that the sidebar width is 200px; */ | ||
width: 190px; | ||
--polkadot-pink: #E6007A; | ||
--polkadot-green: #56F39A; | ||
--polkadot-lime: #D3FF33; | ||
--polkadot-cyan: #00B2FF; | ||
--polkadot-purple: #552BBF; | ||
} | ||
|
||
body nav.sidebar { | ||
flex: 0 0 250px; | ||
body.sdk-docs { | ||
nav.sidebar>div.sidebar-crate>a>img { | ||
width: 190px; | ||
} | ||
|
||
nav.sidebar { | ||
flex: 0 0 250px; | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# Schema: Polkadot SDK PRDoc Schema (prdoc) v1.0.0 | ||
# See doc at https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json | ||
|
||
title: Fix call enum's metadata regression | ||
|
||
doc: | ||
- audience: Runtime Dev | ||
- audience: Runtime User | ||
description: | | ||
This PR fixes an issue where in the metadata of all FRAME-based chains, the documentation for | ||
all extrinsic/call/transactions has been replaced by a single line saying "see Pallet::name". | ||
|
||
Many wallets display the metadata of transactions to the user before signing, and this bug | ||
might have affected this process. | ||
|
||
crates: | ||
- name: frame | ||
- name: frame-support |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters