lucid-package

npm package

0.0.92

Lucid-package now contains more npm run scripts like npm start. There's also more colors to the commandline output.

0.0.91

You can now create packages with an interactive commandline form with templates for commonly used frameworks.

0.0.79

Added support for default values for package settings.

0.0.72

Added support for serving content from a public directory at the root of your extension package.

0.0.31

When using lucid-package bundle, you may now provide an environment param lucid-package bundle --env=staging. Your package will now be bundled with the overrides defined in manifest.staging.json and generate a package-staging.zip.

0.0.29

When using lucid-package test-editor-extension, you may now provide a manifest.local.json alongside your existing manifest.json that overrides values in the manifest.

For example, if you want to use a different callbackBaseUrl in your first dataConnector while debugging locally, your manifest.local.json file would look like this:

inline:json

{
    "dataConnectors": [
        {
            "callbackBaseUrl": "https://debug-data-connector.localhost/connector-name/"
        }
    ]
}

This allows you to always keep production configuration values in your manifest.json file while still allowing you the flexibility to override those values during development.

0.0.26

The OAuth 2.0 client credentials grant type is now supported.

0.0.24

OAuth providers can now be used in development mode without a need to bundle and install the package.
Add a JSON file named <provider name>.credentials.local at the root of your package, containing a JSON object with clientId and clientSecret keys.
This file will be used to allow OAuth requests to be made whenever your extension is being served with lucid-package test-editor-extension.

0.0.23

New packages created with the CLI now include a .gitignore file by default.

0.0.20

Custom shape libraries may now include multiple entries in the library manifest referring to the same shape definition file.
Shape entries in the shape library manifest may now optionally include a "key" to be used to differentiate between them when calling EditorClient.getCustomShapeDefinition.

0.0.14

Dev server is more fault-tolerant while starting up.

0.0.13

Bugfix: Dev server now sends the correct package ID and version for shape libraries.

0.0.11

Editor extension manifests may now specify the CUSTOM_UI scope, which allows for the
creation of custom panels in the right dock in Lucidchart.

0.0.9

Package manifests may now specify product in each entry of editorExtensions. This
can currently be either "chart" or "spark", and defaults to "chart" if omitted.

0.0.8

Package manifests may now include two additional fields, id and oauthProviders.

If specified, id must match the ID of the extension on the Developer Portal, or
uploading a new version of the package will fail. This serves as protection against
developers accidentally uploading a package to the wrong project.

oauthProviders is configuration for OAuth providers that editor extensions may make
API calls to. See the new section on Using OAuth APIs
in the Developer Guide.

For specifying bootstrap data on documents
created via the Lucid OAuth API, you must now
use the package id and editor extension name specified in your manifest even during
development, rather than specifying __local__.

When doing local development of an editor extension, if you already have another version
of that extension installed, the local code will be loaded instead of the installed version.