# Import resources into Code Repositories

:::callout{theme="success"}
The following documentation is specific to TypeScript v1 functions. For more [robust capabilities](../language-feature-support/index.md#typescript-v1-vs-typescript-v2), including support for Ontology SDK and configurable resource requests, we recommend [migrating to TypeScript v2](../typescript-v2-migration/index.md).
:::

The **Resource imports** sidebar in Code Repositories offers a centralized interface to manage imported Foundry resources within your TypeScript functions repository. The sidebar allows you to import, remove, and view details of various resources, including Ontology types, LMS language models, live deployments, and external systems such as REST APIs.

![Resource Imports sidebar](../../../assets/ae1e01e0fc69ddb7f59e69674e6a84bd5e1b326b7ceba4a4e05a9acaaa03f0d4.webp)

## Select an Ontology

An Ontology is required to import object and link types. To choose an Ontology:

1. Choose **Add** to open the resource selector menu, and then choose **Ontology** to begin importing Ontology types. If no Ontology is selected, this will automatically open the Ontology selector dialog.

If you have already imported at least one Ontology type, that type's Ontology is automatically selected. To change the Ontology, choose the **Edit** button next to the selected Ontology's name to open the Ontology selector dialog.

![Ontology selector dialog](../../../assets/e937de1c85c8f6fd161eb89807934946006e0ec9f3bf8dbe429ac663cc164d53.webp)

All imported resources within your repository must be associated with the same Ontology, so importing resources after changing the Ontology will overwrite any existing imports from other Ontologies.

## Import resources

:::callout{theme="warning"}
Modern versions of the TypeScript v1 template maintain the current state of repository imports in a `resources.json` file checked into your repository.

If you encounter warnings about an unresolvable file in the sidebar, see the [file-based ontology imports](#file-based-repository-imports) section for information about the expected file format and troubleshooting steps for resolving the issue.
:::

To import resources using the sidebar:

1. Use the **Add** button in the top right of the sidebar and select the desired resource type. This will open the selector dialog for that resource.
2. Use the search bar and filters to locate the resources you want to import.
3. Choose a resource to display its preview panel with detailed information.
4. Use the **Select** button to add resources to your selection.
5. Expand the cart panel to review your selection and confirm by choosing **Confirm selection**.

After confirming your selection, Code Assist will be restarted to re-run the necessary code generation tasks to apply your changes. Each imported resource is then exposed as a generated package, so you import it from a generated package path rather than a path relative to your own files. For example, Ontology types are imported from `@foundry/ontology-api`; the exact path depends on the resource type.

![Example resource selector dialog](../../../assets/ed653a0c267b89f2e78968ee2d5e7d10d6933ce16d5c97e53db18dda788c6be5.webp)

Learn more about importing resources of a specific type:

* [Ontology types](../ontology-imports/index.md)
* [Language models](../language-models-python-tsv2/index.md#import-a-language-model)
* [Live deployments](../functions-on-models/index.md#import-a-live-deployment-in-a-repository)
* [External sources](../webhooks/index.md)

## Manage imported resources

Resources are categorized by type in the sidebar:

* Ontology: Object, interface, and link types
* Models: LMS models and live deployments
* Sources: External systems such as REST APIs

Choose the corresponding resource icon at the top of the sidebar to filter by type or use the text input to search by name. To remove a resource, hover over the resource icon and choose the **Remove** button. To add or remove multiple resources simultaneously, use a selector dialog. To view more details, select an imported resource to open its preview panel.

Some resource types may have dependencies between other resources. For instance, link types are organized under their respective object types. If an imported resource has dependencies, a message like "(1 link type)" will be displayed next to the resource title. To view a resource's dependencies, hover over the resource icon and select the chevron that appears.

![Resource Imports sidebar filter controls](../../../assets/31dcbcbbeaa64ed3f8b2d9f34f69b0c361f98f69a51f1877e86458443bb9c99c.webp)

## Importing resources without API names

Resources must have an API name to be referenced within code in TypeScript functions repositories. If a resource lacks an API name, a warning is displayed. Hover over the warning sign to learn more or easily configure an API name by choosing **Add API name**.  Alternatively, choose **Learn more** to see documentation about adding an API name tailored to the specific resource type.

![Resource Imports sidebar API name warning](../../../assets/c43554909430612dc86809283f31807d744c6b6930597fd2d74a5690cf942547.webp)

## Import resources with value type dependencies

Some resources depend on [value types](../../object-link-types/value-types-overview/index.md) to define the datatypes used to interact with them, for example, function interfaces. For these resources, their value type dependencies are imported into the repository automatically so that they are available to use along with the resource.

In some cases, importing a combination of such resources can result in a value type dependency conflict. This occurs when different resources have a common value type they depend on at differing versions. It is not possible to have both versions of the same value type imported, and this causes a compilation error. This error is accompanied by a warning in the sidebar, allowing you to view the resources with conflicting dependencies.

![Value type conflicts warning](../../../assets/1b52b32d9f54d99aca23d052568216d518ef836f32138f4ebcbecd8ec14f9107.webp)

## File-based repository imports

Modern versions of the TypeScript v1 template maintain the current state of repository imports using a `resources.json` file checked into your repository. This gives you full Git semantics, allowing you to review, branch, and revert changes to your imports. The resource import sidebar helps you update this file by automatically inserting entries into the `resources.json` file.

If the `resources.json` file is in an invalid state, a warning will appear in the sidebar informing you that the file cannot be processed. If you encounter this error, ensure that your file contains a single JSON object with the following data:

| Field                | Type                                        |
|----------------------|---------------------------------------------|
| `objectTypes`        | Array of `{ rid: string }`                  |
| `linkTypes`          | Array of `{ rid: string }`                  |
| `sources`            | Array of `{ rid: string }`                  |
| `functions`          | Array of `{ rid: string, version: string }` |
| `valueTypes`         | Array of `{ rid: string, version: string }` |
| `functionInterfaces` | Array of `{ rid: string, version: string }` |
| `_comment`           | String                                      |
| `version`\[1]         | Integer                                     |

\[1] The `version` field is used to express the version and format of the `resources.json` file. Currently only `version: 1` is supported. `version: 0` is used to indicate that your repository must undergo a migration from the prior, repository-wide imports workflow. This migration is handled automatically with a patch applied to your repository when a commit with `version: 0` is made.

Because the `resources.json` file is checked into your repository, you can view the commit history and use the history to revert the file back to a working state.

## Enable resource types

By default, some resource types may not be enabled for use in your repository. The enabled resource types are determined by your `functions.json` file. This is the contents of a typical default `functions.json` file.

```json
{
  "useOntologyApiNames" : true,
  "enableModelFunctions" : false,
  "enableModelGraphFunctions" : false,
  "enableDiscoverImproperOntologyAccess": false,
  "enableQueries": false,
  "enableModelMetadata": false,
  "useDeploymentApiNames": true,
  "enableVectorProperties": true,
  "enableTimeSeriesProperties": false,
  "enableExternalSystems": false,
  "enableMediaReferenceProperties": false
}
```

Importing resources without enabling the corresponding flag in your `functions.json` file may cause checks to fail in your repository. To use imported live deployments, set `enableModelFunctions` to true. To use imported sources, set `enableExternalSystems` to true.