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
Consider making sub-modules within shank-idl - such as idl_instruction - public.
Shank does a lot of the heavy lifting for you when it comes to parsing all of your Rust code into an IDL object, complete with serde.
If the rest of the modules were public, this would allow devs to build on top of Shank and customize their IDLs, perhaps by adding additional configurations for their client-side code.
The text was updated successfully, but these errors were encountered:
buffalojoec
changed the title
Consider making sub-modules public
Consider making shank-idl sub-modules public
Mar 26, 2023
Consider making sub-modules within
shank-idl
- such asidl_instruction
- public.Shank does a lot of the heavy lifting for you when it comes to parsing all of your Rust code into an IDL object, complete with
serde
.If the rest of the modules were public, this would allow devs to build on top of Shank and customize their IDLs, perhaps by adding additional configurations for their client-side code.
The text was updated successfully, but these errors were encountered: