Docs: fix UFix64
, Fix64
and Address
in types tables
#1073
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that the
UFix64
andFix64
type arguments are not correctlyrepresented if you pass them as arguments with the
t.UFix256
ort.Fix256
type respectively.After a quick look in
types.js
it seems that the library doesn't evenknow about those types. Passing in
t.UFix64
andt.Fix64
as a typeseems to work just fine.
It also seems that an
Address
typed argument needs to be passed inwith the
t.Address
type instead of thet.String
type as suggestedin the docs.
This PR additionally fixes the formatting/styling for the
path
typeat the very end of the table in the docs.