Contributing to SetupExample

Overview

The project contains a variety of packages that are published and versioned collectively. Each package lives in its own directory in the /packages directory. Each package is self contained, and defines its dependencies in a package.json file.

We use Yarn Workspaces and Lerna for managing and publishing multiple packages in the same repository.

License Notice

Copyright 2022 Splunk, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Getting Started

1. Clone the repo.
2. Install yarn (>= 1.2) if you haven't already: npm install --global yarn.
3. Run the setup task: yarn run setup.

After this step, the following tasks will be available:

• start – Run the start task for each project
• build – Create a production bundle for all projects
• test – Run unit tests for each project
• lint – Run JS and CSS linters for each project
• format – Run prettier to auto-format *.js, *.jsx and *.css files. This command will overwrite files without asking, format:verify won't.

Running yarn run setup once is required to enable all other tasks. The command might take a few minutes to finish.

Switching between Examples

This app contains to different examples, one for a typical setup page that stores a secret in the storage/passwords endpoint, you can switch between these examples by switching which component appears in the Start page. packages/setup-example-app/src/main/webapp/pages/start/index.jsx

Developer Scripts

Commands run from the root directory will be applied to all packages. This is handy when working on multiple packages simultaneously. Commands can also be run from individual packages. This may be better for performance and reporting when only working on a single package. All of the packages have similar developer scripts, but not all scripts are implemented for every package. See the package.json of the package in question to see which scripts are available there.

For more granular control of development scripts, consider using Lerna directly.

Code Formatting

SetupExample uses prettier to ensure consistent code formatting. It is recommended to add a prettier plugin to your editor/ide.