Please note, this type of extension requires Looker 24.0 and above.

This example demonstrates an extension that can be mounted as a tile in a dashboard or an explore. It is primarily a demonstration of the APIs and data that is available to an extension running inside a dashboard.

1. Clone the Looker extension examples repo.

   # cd ~/ Optional, your user directory is usually a good place to git clone to.
   git clone git@github.com:looker-open-source/extension-examples.git
   

2. Navigate (cd) to the example directory on your system

   cd extension-examples/react/javascript/tile-visualization
   

3. Install the dependencies with npm.

   npm install
   

4. Start the development server

   npm run develop
   

   The extension is now running and serving the JavaScript locally at https://localhost:8080/bundle.js.

5. Log in to Looker and create a new project.

   This is found under Develop => Manage LookML Projects => New LookML Project.

   Select "Blank Project" as your "Starting Point". This will create a new project with no files.

   1. The extension folder has a manifest.lkml file.

   Either drag & upload this file into your Looker project, or create a manifest.lkml with the same content. Change the id, label, or url as needed.

   project_name: "tile-sdk"
   
   application: app {
      label: "Tile SDK Demo"
      # file: "bundle.js"
      url: "https://localhost:8080/bundle.js"
      mount_points: {
         dashboard_vis: yes
         dashboard_tile: yes
         standalone: no
      }
      entitlements: {
         local_storage: yes
         use_form_submit: yes
         core_api_methods: []
         external_api_urls: []
         oauth2_urls: []
         scoped_user_attributes: []
         global_user_attributes: []
      }
   }
   

6. Create a model LookML file in your project. The name doesn't matter but the convention is to name it the same as the project — in this case, tile-visualization.

• Add a connection in this model.
• Configure the model you created so that it has access to the selected connection. We do this because Looker permissions data access via models — In order to grant / limit access to an extension, it must be associated with a model.

7. Connect the project to Git. This can be done in multiple ways:

• Create a new repository on GitHub or a similar service, and follow the instructions to connect your project to Git
• A simpler but less powerful approach is to set up git with the "Bare" repository option which does not require connecting to an external Git Service.

8. Commit the changes and deploy them to production through the Project UI.

9. Reload the page and click the Browse dropdown menu. You will see the extension in the list.

• The extension will load the JavaScript from the url provided in the application definition. By default, this is https://localhost:8080/bundle.js. If you change the port your server runs on in the package.json, you will need to also update it in the manifest.lkml.
• Refreshing the extension page will bring in any new code changes from the extension template, although some changes will hot reload.

The process above describes how to run the extension for development. Once you're done developing and ready to deploy, the production version of the extension may be deployed as follows:

1. In the extension project directory build the extension by running npm run build.

2. Drag and drop the generated dist/bundle.js file into the Looker project interface

3. Modify the manifest.lkml to use file instead of url:

   project_name: "tile-sdk"
   
   application: app {
      label: "Tile SDK Demo"
      file: "bundle.js"
      # url: "https://localhost:8080/bundle.js"
      mount_points: {
         dashboard_vis: yes
         dashboard_tile: yes
         standalone: no
      }
      entitlements: {
         local_storage: yes
         use_form_submit: yes
         core_api_methods: []
         external_api_urls: []
         oauth2_urls: []
         scoped_user_attributes: []
         global_user_attributes: []
      }
   }