Skip to content

v7.0.0-rc.0

Pre-release
Pre-release

Choose a tag to compare

@pluma pluma released this 10 Jul 15:17
· 470 commits to main since this release
0fd7083

This is a release candidate which is not intended for use in production and has been published under the npm next tag.

To install the latest preview release, run npm install arangojs@next or yarn add arangojs@next.

This is a major release and breaks backwards compatibility.

Removed

  • Removed statusCode properties of ArangoError and HttpError

    Both of these error types still expose the HTTP status code as the code
    property. For ArangoError the true HTTP status code may be different and
    can still be accessed using the response.statusCode property.

  • Removed ArangoError re-export

    The type can still be imported directly from the error module.

Changed

  • Renamed cursor.nextBatch to cursor.batches.next

  • Renamed cursor.hasMore to cursor.batches.hasMore

  • Renamed db.createArangoSearchView to db.createView

  • Renamed transaction.run to transaction.step

    This should hopefully make it more obvious that sequential calls to arangojs
    methods should be split into separate calls of this method.

  • Added support for View in aql templates (#667)

    View (or ArangoSearchView) objects can now be passed into aql templates
    like ArangoCollection objects.

  • Graph methods now also accept ArangoCollection instances instead of names

    This brings these methods behavior in line with that of the beginTransaction
    and executeTransaction methods of Database objects.

  • Moved collectionToString helper into collection module

  • Moved Dict type into connection module

  • Moved Patch type into documents module

  • Removed Errback type from public API

  • Renamed util/foxx-manifest module to foxx-manifest

  • Removed Collection type from public API

    All public APIs reference DocumentCollection and EdgeCollection directly.

Added

  • Added precaptureStackTraces configuration option (#599)

    This option can be used to get more useful stack traces but results in a
    performance hit on every request.

  • Added cursor.batches to provide a batch-wise cursor API

  • Added before and after to the agentOptions configuration option (#585)

    These methods can be used to track performance metrics for outgoing requests.