You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They should be able to jump to definiton of @using or checkExternalCaller (latter having the hover) to see more doc.
Currently the annotations are defined in Parser file in the full node, but we only have the keys as String.
We could have something similar to BuiltIn, where doc comes alongside the types.
I also show in ralph-lsp that we can find the corresponding annotation and doc when requesting definition of checkExternalCaller.
So I think we could have something similar to the built-in function and std-interface. We could store in the dependencies annotation file so user can jump there to see more info.
We need to check how we choose to represent those annotations, but we could do something similar to scala nowarn annotation
InterfaceFunctionUsingAnnotation{// doc for using annotation
fn using(// doc for preapprovedAssetspreapprovedAssets:Bool,// doc for assetsInContractassetsInContract:Bool,// doc for payToContractOnlypayToContractOnly:Bool,// doc for checkExternalCallercheckExternalCaller:Bool,// doc for updateFieldsupdateFields:Bool,// doc for methodIndexmethodIndex:U256) -> ()}
It has to compile otherwise ralph-lsp will complain.
The text was updated successfully, but these errors were encountered:
For new comers, it would be nice if they could get more information about annotations. for example in:
They should be able to jump to definiton of
@using
orcheckExternalCaller
(latter having thehover
) to see more doc.Currently the annotations are defined in Parser file in the full node, but we only have the
keys
asString
.We could have something similar to BuiltIn, where doc comes alongside the types.
I experimented a bit by first extracting RalphAnnotation in a separate file and then adding some doc field to the annotation.
I also show in ralph-lsp that we can find the corresponding annotation and doc when requesting definition of
checkExternalCaller
.So I think we could have something similar to the built-in function and std-interface. We could store in the dependencies annotation file so user can jump there to see more info.
We need to check how we choose to represent those annotations, but we could do something similar to scala nowarn annotation
It has to compile otherwise
ralph-lsp
will complain.The text was updated successfully, but these errors were encountered: