Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • luisterdoos luisterdoos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Hanze
  • 4.2 GAC Luisterdoos
  • luisterdoosluisterdoos
  • Wiki
  • Frontend plugins: Settings

Frontend plugins: Settings · Changes

Page history
R.deVries created page: Frontend plugins: Settings authored Dec 14, 2017 by Robert de Vries's avatar Robert de Vries
Show whitespace changes
Inline Side-by-side
Frontend-plugins:-Settings.md 0 → 100644
View page @ e5ae6c56
# Frontend plugins
## Settings
You may include settings pages for your plugins. They must reside in the `settings` folder in your plugin.
The naming of your settings page components can be anything you want. There's no guidelines on the naming schemes besides being CamelCase, but it's recommended to include at least your plugin name and append `Settings`. This ensures there won't be any naming conflicts with other plugins.
The structure would look like this:
```bash
.
├── plugins
│   ├── EmailPlugin
│   │   ├── settings
│   │   │   └── EmailSettings.vue
```
A Settings component must specify the following data in its default export object in order for it to automatically show up on the application's settings:
* `settingsMenuItem`
Example code:
```javascript
export default {
name: 'EmailSettingsPage', // must match the filename
settingsMenuItem: {
label: 'E-mail',
icon: 'email'
},
// ... other VueJS code
}
```
You may omit these data points if you don't want to page to show up in the application's settings menu. That might be desirable if it's a child of another settings page, for example.
\ No newline at end of file
Clone repository
  • Frontend plugins: Settings
  • Frontend plugins: speech
  • Frontend plugins: wallpapers
  • Frontend plugins: widgets
  • frontend plugins
  • Home