Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrading from
0.41.13
to0.42.14
- Changelog0.42.14
fix:
The OpenAPI importer now correctly propagates the title field ononeof
schemas.0.42.13
fix:
Example generation now intelligently truncates container examples, for example if the depth limit will be reached on a list of objects,the list will be returned as an empty list, as opposed the previous behavior where an unknown object would be created.
0.42.12
fix:
Previously, deploying docs from Windows machines led to bad asset paths.Now, the CLI respects Windows paths during run and web paths for retrieving
assets.
0.42.11
fix:
The API V2 configuration now supports disabling using titles as schemanames. You may want to disable this flag if your OpenAPI adds the same
title to multiple schemas.
0.42.10
fix:
Previously, the OpenAPI converter would bring overtitle
on everysingle property. This field is extraneous, so now we ignore it.
16 additional updates, see more
0.42.9
fix:
Previously, the OpenAPI importer would ignore skip parsing arbitrarycontent types "/". Now it treats this content type as application/json.
0.42.8
fix:
The API V2 configuration (in beta) now supports global header overrides.This fixes a bug where those header overrides were getting dropped in
certain cases.
0.42.7
feat:
The API V2 configuration (in beta) now supports global headeroverrides. To specify global headers that are not in your
OpenAPI spec, simply add the following block in your
generators.yml
:0.42.6
fix:
Removes extraneous conditional error within namespacing configuration0.42.5
feat:
Adds additional metadata retrievable byfern generator get
so you can now get the langauage and the target repo.0.42.4
fix:
Namespaced APIs now:x-fern-sdk-group-name
annotation for endpoints0.42.3
fix:
The OpenAPI importer now supports handling encoding on multipart requests.Previously, the generators would not respect the
contentType
field foreach form input. But, now they do.
fix:
The OpenAPI importer now correctly parses descriptions of multipartform requests. Previously these descriptions would be ignored.
For example, previously the description
The file to upload
would beignored in the example below.
0.42.2
fix:
Error bodies are now appropriately namespaced as well!0.42.1
fix:
Make sure to check for optionality when parsing stdout and stderr in CLI. Thisremoves the error:
Cannot read properties of undefined (reading 'includes')
.0.42.0
fix:
If you merge multiple OpenAPI specs with namespaces,fern check
will no longercomplain about duplicate schema names across namespaces.
In the example below, both OpenAPI specs can have duplicative schema names and
that is okay.
0.42.0-rc0
feat:
The Fern Definition now supportsconten-type
on multipart request properties.For example, to specify an
application/octet-stream
andapplication/json
contnet types, use the snippet below:
0.41.16
fix:
Previously the OpenAPI converter would incorrectly markthe values of
additionalProperties
as optional. Now, we haveintroduced a feature flag to turn this behavior off.
The feature flag can be configured in generators.yml:
0.41.15
internal:
Performance improvements for stringifiying large Intermediate Representations. Ifyou have a large OpenAPI spec or Fern Definition, this can potentially shave off
minutes from
fern generate
.0.41.14-rc2
internal:
Remove bang operator and fix eslint warning incompatible-ir-versions.ts
.0.41.14-rc1
feat:
Runningfern check
will now check to confirm that the generator versions you are running are compatible with your Fern CLI version.Each version of SDK generators depends on a version of a libary that is exported by the Fern CLI, and as a result, each generator has a minimum
compatible version of the Fern CLI. As an example, if you were to run
fern check
while leveragingfernapi/fern-python-sdk
version2.0.0
, on CLI version0.1.3
, you'd receive the following error:The generator fernapi/fern-python-sdk requires CLI version 0.23.0-rc4 or later (current version: 0.1.3-rc0).
Indicating that you must upgrade your CLI in order to leverage the current generator.
0.41.14-rc0
fix:
The Fern CLI now safely handles a npx file exists error by retrying the command on failure.This error typically happens when two or more instances of the Fern CLI are running
npx
at the same time.