<aside> 👉 For an overview of import requirements and how to import code components and design tokens from your repo, please see Import Overview
By default when you run the CLI, it bundles your code and aims to generate config for all your components, all their props, all their available metadata and all matching presets (according to your import settings).
If our code repo is the source of truth, why curate the import?
There are a few common reasons why you'd want to curate the 'everything' imported by default:
Curating your import is optional - you can leave your components and props configuration unchanged and work with them in Figma and Interplay as imported.
There are 3 ways of curating your imported configuration as outlined below.
You can use a combination of these to manage different parts of your configuration.
<aside> 👉 You don't need to modify your component code for Interplay - your components should be the same as you use in your production applications.
Perhaps the most convenient way of changing your configuration is by updating the imported configuration online in your Project.
For example you can:
Updates you make to imported configuration via the Interplay UI are treated as overrides of the underlying 'truth' - the config received from the code repo. These overrides are preserved and re-applied to future imports unless the same setting is later changed in the code, in which case "code change wins" and the UI override is discarded.
For more details about editing components and tokens you have imported into your project, see Projects
An alternative approach to curating imported items is to update the generated configuration before it gets to Interplay - effectively sending a different 'truth' to Interplay about what your repo looks like.
We make these modifications in a way that is applied every run of the import, e.g.:
Applying these modifications each run means we can still run the import repeatedly to keep Interplay up to date over time.