-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve documentation signature mismatches #1993
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I just had a minor comment.
@@ -1039,7 +1039,6 @@ super.init(); | |||
|
|||
/** | |||
* Asynchronously fetches events emitted by this {@link SmartContract} and returns an array of events with their corresponding types. | |||
* @async |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch.
@@ -836,7 +839,7 @@ class Field { | |||
* | |||
* **Important**: If the given `bytes` array is an array of `booleans` or {@link Bool} elements that all are `constant`, the resulting {@link Field} element will be a constant as well. Or else, if the given array is a mixture of constants and variables of {@link Bool} type, the resulting {@link Field} will be a variable as well. | |||
* | |||
* @param bytes - An array of {@link Bool} or `boolean` type. | |||
* @param bits - An array of {@link Bool} or `boolean` type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see what you did here, but the doc comment above says "If the given bytes
array is an array of ...". Should we make the comment and @param name consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good eye. Yeah, I updated bytes to bits in all cases. Bits seems like the correct word to use here.
This PR resolves two classes of validation warnings from the typedoc build: signature mismatches, and not exported warnings.
Not exported warnings occur in a case like this:
We make liberal use of this pattern, and I don't see a problem with continuing to do so. We would only respect this warning if we were committed to a 100% complete autogenerated o1js reference.