Voyager 2
2.x
2.x
  • Introduction
  • Javascript
  • Media Manager
  • Plugins
  • Settings
  • bread
    • Actions
    • BREAD Builder
    • Layouts
    • Lists
    • Manipulate data
    • Multilanguage
    • Relationships
    • Validation
    • Views
  • contributing
    • Assets
    • CSS
    • Introduction
  • de
    • index
  • formfields
    • Checkboxes
    • Date & Time
    • Dynamic input
    • Formfields
    • Media Picker
    • Number
    • Password
    • Radios
    • Relationship
    • Repeater
    • Select
    • Simple array
    • Slider
    • Slug
    • Tags
    • Text
    • Toggle
  • getting-started
    • Installation
    • Prerequisites
    • Tips and tricks
    • What is Voyager
  • overriding
    • Overriding formfields
    • Icons
  • plugins
    • Assets
    • Components
    • Features
    • Filter
    • Plugin development
    • Language
    • Menu Items
    • Custom pages
    • Preferences
    • Routes
    • Settings
    • Widgets
Powered by GitBook
On this page
  • Tests
  • Coverage
  • Developing Javascript and CSS
  • Breaking changes

Was this helpful?

  1. contributing

Introduction

PreviousCSSNextde

Last updated 3 years ago

Was this helpful?

Thanks for contributing to Voyager! Here are some important things to keep in mind:

Tests

It is important to provide testing for all newly introduced code if possible.

Coverage

We let check our test coverage.

Developing Javascript and CSS

If you want to change anything related to Javascript and/or CSS, you can make your life easier by using hot module reloading. Hot module reload allows you to change code and instantly see the changes you made without the need to reload your browser window or clearing your cache.

To do so, you first have to install all NPM modules by running npm install. After that run npm run watch to provide a dev-server serving the compiled assets. Now you can enable using this server by calling the command php artisan voyager:dev --enable or by going to the Settings => Admin and changing the Dev-Server setting to Yes.

When you are done, you can simply change the setting to No, call php artisan voyager:dev --disable or click Disable on the notification that appears when your dev-server becomes unavailable.

Breaking changes

...

code climate