Skip to content

ccappetta/player-googlemaps

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

A small webpack based boilerplate for creating custom Boomi Flow UI components.

Setup

  • Download or clone this repo
  • npm install

Writing a Custom Component

Create the custom component in index.tsx, or in separate .tsx files and import them into index.tsx. Any custom styles can be added in index.css.

Testing

You can start the local development server with npm run dev. This will serve the compiled javascript and css at http://localhost:8080/custom-component.js and http://localhost:8080/custom-component.css.

The easiest way to test a custom component would be to create a custom player then add references to the custom-component.js and custom-component.css as custom resources, more information on loading custom resources can be found here: https://docs.manywho.com/adding-custom-javascript-and-stylesheets/

The local development server won't be accessible from flow.manywho.com, you can workaround this by using a tunnel like https://ngrok.com/download

Run ngrok with:

ngrok http 8080 -host-header="localhost:8080"

If that fails then try:

ngrok http --host-header=rewrite 8080

ngrok will provide a url like https://ad7c2b13.ngrok.io that will point to http://localhost:8080, for example you would add the following as custom resources in a player:

https://ad7c2b13.ngrok.io/custom-component.js,
https://ad7c2b13.ngrok.io/custom-component.css

After making changes to your custom component you can refresh the browser running the flow for the changes to be picked up.

Deploying

Run the npm run build command to create a production build of custom-component.js and custom-component.css. You can then host these two files either by using the built in Assets support (more information can be found here: https://docs.manywho.com/everything-you-want-to-know-about-assets/) or a 3rd party file hosting environment.

After the .js and .css files are available from a file host you can reference them in a custom player as custom resources.

Configuration

You can change the generated filenames from custom-component.js and custom-component.css by editing the webpack.config.js file:

  • line 6 for custom-component.js
  • line 36 for custom-component.css

About

No description or website provided.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 78.0%
  • JavaScript 14.1%
  • CSS 7.9%