Finsemble: CHANGELOG

Change Log

0.4.1 - 2017-05-19

  • Added placeholder and hooks for authentication. See the Enabling Authentication Tutorial for instructions on building your own authentication component. The tutorial also includes information on disabling authentication.
  • The authentication placeholder (i.e. the included sample code) prompts for username and password on startup. All storage is now keyed off the username, so the configuration of the application is determined by the entered username (new usernames automatically become new users). The password field is ignored in the placeholder....any password works.

0.4 - 2017-05-02

0.3.1 - 2017-04-21

Minor bug fixes

Fixes

  • Direct chat component to the correct url.
  • Fix some icons issues in the toolbar and windows taskbar.

0.3.0 - 2017-04-19

You may be wondering, "Where is 0.2?" The short answer is that Brad messed up bumping the npm version. So 0.3.0 is what we're working with. Hope you enjoy the new features!

Added

  • User defined components - Through the App Launcher, a user can now add their own components (Your own web pages,Google,CNN,etc) and see them in the App Launcher.Currently, these do not persist in workspaces.
  • Allow developers to set UUID, Port, and host for local, dev, staging, and prod environments.
  • Added way for users to add storage adaptors.
  • Added support for hosting finsemble apps on relative paths.
  • Cleaned up top-level api responses (you should parse response instead of response.data inside of API Calls. If responding to a router request, still parse response.data).
  • Workspaces can be pinned.
  • New look and feel for the toolbar, window header, and dialogs.
  • bug fixes.

Changed

  • Documentation fixes.

Migration steps

We're aware that making changes to your project's structure is a huge pain - we certainly don't intend on making this process commonplace. For this release, however, there are several changes to the underlying application bootstrapping/build process.

There are two paths to migration:

  1. Copying the components that you've already created into a fresh copy of the seed project, or
  2. Modifying your project to match the new configuration.

Copying Components

  1. Clone the seed project into a different folder.
  2. Run npm install.
  3. run npm update -g @chartiq/finsemble-cli
  4. Use the CLI to create your components.
  5. Copy src/components from your old seed into the root of your new project.

Try to run npm run dev. Contact us if this doesn't work and we'll jump on a call to figure out what isn't set up properly.

Modifying your existing project.

  1. Replace src/node_fileserver/FinsembleConfigs.js with the file in the seed project on the master branch.
  2. create configs/startup.json; copy contents from the master branch of the seed project and put in the desired port/hostname configuration.
  3. Modify gulpfile.js

    • On line 9 paste var StartupConfig = require("./configs/startup");. Make sure to update any locations using a port number to the use startup config.
    • Replace line 143 (configPath inside of the launchOpenfin command) with configPath: StartupConfig[env].serverConfig.
    • In the gulp task devServer change launchOpenfin() to launchOpenfin("dev") Also, change all launchOpenfin function calls to the correct environment. The will match up to your startup config.
  4. run npm install.

  5. run npm update -g @chartiq/finsemble-cli;
  6. run npm update @chartiq/finsemble;
  7. run npm run dev. If it doesn't work, contact us and we'll jump on a call with you.

We apologize for the extensive changes. It's unlikely that we'll do this to you again.

The Finsemble Dev Team.

Misc Integration notes:

  1. If you have components from a previous release, that you based on our tutorial on building an application, make sure to remove this rule from your CSS.
* {
    display: block;
}

If you don't, you'll get some lovely CSS plastered on the background of your component's DOM.

  1. If you're playing with accountList/accountDetail from the tutorial, make sure your call to LauncherClient.getActiveDescriptors parses response instead of response.data.