Skip to content
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

Consider making shank-idl sub-modules public #49

Open
buffalojoec opened this issue Mar 26, 2023 · 0 comments
Open

Consider making shank-idl sub-modules public #49

buffalojoec opened this issue Mar 26, 2023 · 0 comments

Comments

@buffalojoec
Copy link

buffalojoec commented Mar 26, 2023

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.

@buffalojoec buffalojoec changed the title Consider making sub-modules public Consider making shank-idl sub-modules public Mar 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant