-
Notifications
You must be signed in to change notification settings - Fork 64
Add options to configure how traits are rendered in Rust #242
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
Changes from 22 commits
9c26abf
d58f1ca
370588d
b2fafa7
e65f80d
3b82f67
1d87bd9
439f68e
4294c50
b1e5d85
ce8643b
a2fc483
5ebb815
ed43f34
346048e
ce131ec
64b556d
096a979
841cbc2
1e6d7c3
6815f2d
962c66c
91cb4c8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@codama/renderers-rust': patch | ||
| --- | ||
|
|
||
| Add options to configure how traits are rendered in Rust |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,12 +37,112 @@ codama.accept(renderVisitor(pathToGeneratedFolder, options)); | |
|
|
||
| The `renderVisitor` accepts the following options. | ||
|
|
||
| | Name | Type | Default | Description | | ||
| | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ||
| | `deleteFolderBeforeRendering` | `boolean` | `true` | Whether the base directory should be cleaned before generating new files. | | ||
| | `formatCode` | `boolean` | `false` | Whether we should use `cargo fmt` to format the generated code. When set to `true`, the `crateFolder` option must be provided. | | ||
| | `toolchain` | `string` | `"+stable"` | The toolchain to use when formatting the generated code. | | ||
| | `crateFolder` | `string` | none | The path to the root folder of the Rust crate. This option is required when `formatCode` is set to `true`. | | ||
| | `linkOverrides` | `Record<'accounts' \| 'definedTypes' \| 'instructions' \| 'pdas' \| 'programs' \| 'resolvers', Record<string, string>>` | `{}` | A object that overrides the import path of link nodes. For instance, `{ definedTypes: { counter: 'hooked' } }` uses the `hooked` folder to import any link node referring to the `counter` type. | | ||
| | `dependencyMap` | `Record<string, string>` | `{}` | A mapping between import aliases and their actual crate name or path in Rust. | | ||
| | `renderParentInstructions` | `boolean` | `false` | When using nested instructions, whether the parent instructions should also be rendered. When set to `false` (default), only the instruction leaves are being rendered. | | ||
| | Name | Type | Default | Description | | ||
| | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ||
| | `deleteFolderBeforeRendering` | `boolean` | `true` | Whether the base directory should be cleaned before generating new files. | | ||
| | `formatCode` | `boolean` | `false` | Whether we should use `cargo fmt` to format the generated code. When set to `true`, the `crateFolder` option must be provided. | | ||
| | `toolchain` | `string` | `"+stable"` | The toolchain to use when formatting the generated code. | | ||
| | `crateFolder` | `string` | none | The path to the root folder of the Rust crate. This option is required when `formatCode` is set to `true`. | | ||
| | `linkOverrides` | `Record<'accounts' \| 'definedTypes' \| 'instructions' \| 'pdas' \| 'programs' \| 'resolvers', Record<string, string>>` | `{}` | A object that overrides the import path of link nodes. For instance, `{ definedTypes: { counter: 'hooked' } }` uses the `hooked` folder to import any link node referring to the `counter` type. | | ||
| | `dependencyMap` | `Record<string, string>` | `{}` | A mapping between import aliases and their actual crate name or path in Rust. | | ||
| | `renderParentInstructions` | `boolean` | `false` | When using nested instructions, whether the parent instructions should also be rendered. When set to `false` (default), only the instruction leaves are being rendered. | | ||
| | `traitOptions` | [`TraitOptions`](#trait-options) | `DEFAULT_TRAIT_OPTIONS` | A set of options that can be used to configure how traits are rendered for every Rust types. See [documentation below](#trait-options) for more information. | | ||
|
|
||
| ## Trait Options | ||
|
|
||
| The Rust renderer provides sensible default traits when generating the various Rust types you client will use. However, you may wish to configure these traits to better suit your needs. The `traitOptions` attribute is here to help you with that. Let's see the various settings it provides. | ||
|
|
||
| ### Default traits | ||
|
|
||
| Using the `traitOptions` attribute, you may configure the default traits that will be applied to every Rust type. These default traits can be configured using 4 different attributes: | ||
|
|
||
| - `baseDefaults`: The default traits to implement for all types. | ||
| - `dataEnumDefaults`: The default traits to implement for all data enum types, in addition to the `baseDefaults` traits. Data enums are enums with at least one non-unit variant — e.g. `pub enum Command { Write(String), Quit }`. | ||
| - `scalarEnumDefaults`: The default traits to implement for all scalar enum types, in addition to the `baseDefaults` traits. Scalar enums are enums with unit variants only — e.g. `pub enum Feedback { Good, Bad }`. | ||
| - `structDefaults`: The default traits to implement for all struct types, in addition to the `baseDefaults` traits. | ||
|
|
||
| Note that you must provide the fully qualified name of the traits you provide (e.g. `serde::Serialize`). Here are the default values for these attributes: | ||
|
|
||
| ```ts | ||
| const traitOptions = { | ||
| baseDefaults: [ | ||
| 'borsh::BorshSerialize', | ||
| 'borsh::BorshDeserialize', | ||
| 'serde::Serialize', | ||
| 'serde::Deserialize', | ||
| 'Clone', | ||
| 'Debug', | ||
| 'Eq', | ||
| 'PartialEq', | ||
| ], | ||
| dataEnumDefaults: [], | ||
| scalarEnumDefaults: ['Copy', 'PartialOrd', 'Hash', 'num_derive::FromPrimitive'], | ||
| structDefaults: [], | ||
| }; | ||
|
Comment on lines
+67
to
+81
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think there's a case to be made for the default being zero traits and zero scalar enum configurations, but I don't feel too strongly about it.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We had to keep them like that in order to avoid introducing breaking changes. This produces code in the exact same way we were before. But I think these are sensible defaults for most clients, right?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sure, it doesn't really hurt to just let people change the base defaults anyway, and avoid the breaking change. |
||
| ``` | ||
|
|
||
| ### Overridden traits | ||
|
|
||
| In addition to configure the default traits, you may also override the traits for specific types. This will completely replace the default traits for the given type. To do so, you may use the `overrides` attribute of the `traitOptions` object. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Slick, I like it! |
||
|
|
||
| This attribute is a map where the keys are the names of the types you want to override, and the values are the traits you want to apply to these types. Here is an example: | ||
|
|
||
| ```ts | ||
| const traitOptions = { | ||
| overrides: { | ||
| myCustomType: ['Clone', 'my::custom::Trait', 'my::custom::OtherTrait'], | ||
| myTypeWithNoTraits: [], | ||
| }, | ||
| }; | ||
| ``` | ||
|
|
||
| ### Feature Flags | ||
|
|
||
| You may also configure which traits should be rendered under a feature flag by using the `featureFlags` attribute. This attribute is a map where the keys are feature flag names and the values are the traits that should be rendered under that feature flag. Here is an example: | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like this even more! |
||
|
|
||
| ```ts | ||
| const traitOptions = { | ||
| featureFlags: { fruits: ['fruits::Apple', 'fruits::Banana'] }, | ||
| }; | ||
| ``` | ||
|
|
||
| Now, if at any point, we encounter a `fruits::Apple` or `fruits::Banana` trait to be rendered (either as default traits or as overridden traits), they will be rendered under the `fruits` feature flag. For instance: | ||
|
|
||
| ```rust | ||
| #[cfg(feature = "fruits", derive(fruits::Apple, fruits::Banana))] | ||
lorisleiva marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| ``` | ||
|
|
||
| By default, the `featureFlags` option is set to the following: | ||
|
|
||
| ```ts | ||
| const traitOptions = { | ||
| featureFlags: { serde: ['serde::Serialize', 'serde::Deserialize'] }, | ||
| }; | ||
| ``` | ||
|
|
||
lorisleiva marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ### Using the Fully Qualified Name | ||
|
|
||
| By default, all traits are imported using the provided Fully Qualified Name which means their short name will be used within the `derive` attributes. | ||
|
|
||
| However, you may want to avoid importing these traits and use the Fully Qualified Name directly in the generated code. To do so, you may use the `useFullyQualifiedName` attribute of the `traitOptions` object by setting it to `true`: | ||
|
|
||
| ```ts | ||
| const traitOptions = { | ||
| useFullyQualifiedName: true, | ||
| }; | ||
| ``` | ||
|
|
||
| Here is an example of rendered traits with this option set to `true` and `false` (which is the default): | ||
|
|
||
| ```rust | ||
| // With `useFullyQualifiedName` set to `false` (default). | ||
| use serde::Serialize; | ||
| use serde::Deserialize; | ||
| // ... | ||
| #[derive(Serialize, Deserialize)] | ||
|
|
||
| // With `useFullyQualifiedName` set to `true`. | ||
| #[derive(serde::Serialize, serde::Deserialize)] | ||
| ``` | ||
|
|
||
| Note that any trait rendered under a feature flag will always use the Fully Qualified Name in order to ensure we only reference the trait when the feature is enabled. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,4 @@ | ||
| export * from './codecs'; | ||
| export * from './linkOverrides'; | ||
| export * from './render'; | ||
| export * from './traitOptions'; |
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.
micro-micro-nit: