demf-custom-operators
v3.0.0
Published
The Custom Operators microfrontend displays and manages a table list of custom operators (user-defined transformations/functions) with search, filter, create, edit, delete, and test functionalities. Allows users to extend the DME with custom logic for use
Readme
Digital Enabler Custom Operators
The Custom Operators microfrontend displays and manages a table list of custom operators (user-defined transformations/functions) with search, filter, create, edit, delete, and test functionalities. Allows users to extend the DME with custom logic for use in mashups and flows.
Built with Vue 3, Vuetify 3, and Vite. Designed for Single-SPA integration.
📌 See also:
📦 Installation
Via CDN
This project is available from the following CDN:
https://cdn.jsdelivr.net/npm/demf-custom-operators@latest/mf-app.jsAdd it to your root-config import map:
{
"imports": {
"demf-custom-operators": "https://cdn.jsdelivr.net/npm/demf-custom-operators@latest/mf-app.js"
}
}🚀 Quick Start
Prerequisites
Before you continue you need to have:
- A Digital Enabler root-config application running
- Single-SPA layout engine configured
- A configuration file for the custom-operators (see below)
Integration Steps
1. Add to Import Map
In your root-config importmap.json:
{
"imports": {
"demf-custom-operators": "https://cdn.jsdelivr.net/npm/demf-custom-operators@latest/mf-app.js"
}
}For local development:
{
"imports": {
"demf-custom-operators": "http://localhost:9017/mf-app.js"
}
}2. Register in Layout
In your root-config layout HTML:
<application
name="demf-custom-operators"
props="realm, palette, custom-operators-config">
</application>3. Create Configuration File
Create a custom-operators-config.json file with these settings:
{
"name": "custom-operators",
"mf": "demf-custom-operators",
"api": "https://[generic_api_location]/api"
}This JSON file must be:
- Stored in a location accessible to the root-config
- Included in the root-config's remote configuration
- Passed as the
custom-operators-configprop to the microfrontend
📖 For details on configuration management, see:
⚙️ Configuration
The Custom Operators microfrontend receives a configuration object via the custom-operators-config prop:
{
"name": "custom-operators",
"mf": "demf-custom-operators",
"api": "https://your-api-endpoint.com/api"
}Configuration Fields
| Field | Type | Required | Description |
|-------|------|----------|-------------|
| mf | string | Yes | Microfrontend identifier (use "demf-custom-operators") |
| api | string | Yes | Base URL for API calls |
Additional Props from Root-Config
The microfrontend also receives these props automatically from the root-config:
realm: Current tenant/realm identifierpalette: Dynamic theme colors (primary, secondary, etc.)
These props are used to:
- Apply consistent theming across the platform
- Configure tenant-specific behavior
- Adapt the Custom Operators appearance to the current application theme
🛠️ Development
Prerequisites
Before you continue you need to have:
- NPM installed
- Node.js (v22+ or v24.8+) installed
- Vue.js and Vite knowledge
- A GitHub account
- Visual Studio Code or IntelliJ IDEA as your development IDE
Project Management
Installation
Open a Terminal window in the project folder and go inside the app folder, then launch:
npm installNOTE: When install finishes, do not worry about warnings on versions and vulnerability problems reported. DO NOT launch
npm audit fixornpm audit fix --forcecommands.
Development Server (with hot-reload)
npm run devThis command:
- Generates Vuetify locales automatically (via
predevscript) - Builds the microfrontend in watch mode
- Starts a preview server at
http://localhost:9017
The microfrontend will be available at: http://localhost:9017/mf-app.js
Build for Production
npm run buildThis command:
- Generates Vuetify locales automatically (via
prebuildscript) - Creates an optimized production build in the
dist/folder - Outputs a SystemJS bundle ready for deployment
Code Quality
npm run lint # Lint and fix files with ESLint
npm run format # Format code with PrettierNOTE: Alternatively to the commands indicated above you can use the Vue UI browser interface.
🌐 Internationalization
The Custom Operators microfrontend supports multiple languages through vue-i18n with automatic Vuetify locale integration.
How It Works
- Locale files are stored in
src/locales/*.json(e.g.,en.json,it.json) - The script
scripts/generate-vuetify-locales.mjsautomatically scans these files - Matching Vuetify translations are imported and merged
- The active language is read from
localStorage.getItem('lang')(defaults toen)
Supported Languages
The Custom Operators includes translations for the languages defined in src/locales/:
- English (
en) - Italian (
it) - [Add other languages as needed]
Adding a New Language
- Create a new file:
src/locales/<code>.json(e.g.,es.json) - Add your translations following the existing structure
- Run
npm run devornpm run build - The generator will automatically include Vuetify translations for that language
🎨 Features
- Dynamic theming: Automatically adapts to the palette passed from root-config
- Multi-language support: Full internationalization with vue-i18n
- Responsive design: Works seamlessly on mobile, tablet, and desktop
- Material Design: Built with Vuetify 3 components and Material Design Icons
- Consistent branding: Shows uniform Custom Operators across all Digital Enabler services
- Platform information: Displays version, copyright, and relevant links
📁 Project Structure
demf-custom-operators/
├── app/
│ ├── src/
│ │ ├── App.vue # Main component
│ │ ├── main.js # Entry point
│ │ ├── components/ # Custom Operators components
│ │ ├── locales/
│ │ │ ├── i18n.js # i18n configuration
│ │ │ ├── en.json # English translations
│ │ │ ├── it.json # Italian translations
│ │ │ └── vuetify-generated.js # Auto-generated Vuetify locales
│ │ ├── plugins/
│ │ │ └── vuetify.js # Vuetify configuration
│ │ ├── router/
│ │ └── store/
│ ├── scripts/
│ │ └── generate-vuetify-locales.mjs
│ ├── public/
│ ├── dist/ # Build output
│ ├── package.json
│ ├── vite.config.js
│ └── eslint.config.js
├── docker/
└── README.md🔍 Troubleshooting
Custom Operators not visible
- Verify the import map includes
demf-custom-operators - Check the layout HTML has the
<application>tag with correct name - Ensure the bundle is accessible at the configured URL
- Look for console errors in the browser developer tools
Configuration not working
- Check that
custom-operators-configprop is passed in the layout - Verify the configuration JSON structure matches the expected format
- Ensure the root-config is loading the remote configuration correctly
- Check console for warnings about missing configuration
Styling issues
- Ensure the
paletteprop is being passed from root-config - Verify Material Design Icons fonts are loaded
- Check that Vuetify theme configuration is correct
- Clear browser cache and reload
API connection errors
- Verify the
apifield incustom-operators-config.jsonis correct - Check network tab for failed API requests
- Ensure CORS is properly configured on the backend
- Verify the API endpoint is accessible from the browser
Development server not starting
- Check that port 9017 is not already in use
- Verify Node.js version is compatible (v22+ or v24.8+)
- Try removing
node_modulesand runningnpm installagain - Ensure all dependencies are correctly installed
📚 Tech Stack
Runtime Dependencies
- Vue 3 (^3.5.22) - Progressive JavaScript framework
- Vuetify 3 (^3.10.7) - Material Design component library
- Single-SPA Vue (^3.0.1) - Single-SPA integration for Vue
- Vue Router (^4.6.3) - Official router for Vue.js
- Vue i18n (^9.14.5) - Internationalization plugin
- Vuex (^4.1.0) - State management
- Axios (^1.13.0) - HTTP client
- Material Design Icons (^7.4.47) - Icon library
Development Dependencies
- Vite (^7.1.12) - Next generation frontend tooling
- ESLint (^9.38.0) - Code linting
- Prettier (^3.6.2) - Code formatting
- Vite Plugin Vue DevTools (^8.0.3) - Vue DevTools integration
- Concurrently (^9.2.1) - Run multiple commands
For complete dependencies, see package.json.
📖 Related Documentation
- Digital Enabler Root Config Template
- Digital Enabler Microfrontend Template
- Single-SPA Documentation
- Vue 3 Documentation
- Vuetify 3 Documentation
- Vite Documentation
📄 License
This project is part of Digital Enabler Ecosystem.
© 2025 Engineering Ingegneria Informatica S.p.A.
🆘 Support
For support, questions, or issues:
- Open an issue on GitHub
- Contact the Digital Enabler development team
- Check the Digital Enabler documentation
