Files
threshold-ui/addons/rose
Cameron Perera c62eb751e4 Icu 6680 UI code editor for secrets (#1499)
* feat: 🎸 initial secret editor

* feat: 🎸 Create Secret Editor for JSON Credentials

✅ Closes: ICU-6680

* style: 💄 Fix sass lint errors

* style: 💄 Appease sass-lint rule for using --size in stylesheet

* refactor: 💡 Set Icon size via component attribute

* refactor: 💡 remove computed decorators for Secret Editor

* refactor: 💡 update editor styles to using sizing variables

* refactor: 💡 update styles and add comments

* refactor: 💡 clean up styling for secret editor

* refactor: 💡 update class names to be more verbose

* chore: 🤖 move jsonlint import to rose index.js

* refactor: 💡 remove duplicate margin style for skeleton body

* refactor: 💡 add comments to SecretEditor component class

* refactor: 💡 large updates to secret json editor

* refactor: 💡 Move JSON Secret to form/field/ directory

* style: 💄 fix padding for Secret Editor line numbers

* chore: 🤖 disable property-sort-oder in .sasslintrc

* refactor: 💡 reorder app.scss styles

* test: 💍 Add integration tests for JSON Secret and Skeleton
2022-12-02 13:58:04 -06:00
..
2022-11-17 13:38:51 -08:00
2022-02-25 09:54:56 -08:00
2022-11-16 10:07:40 -08:00
2022-10-06 11:41:12 -04:00
2022-02-25 09:54:56 -08:00
2022-02-25 09:54:56 -08:00
2022-02-25 09:54:56 -08:00
2021-10-13 16:54:18 -07:00
2022-06-08 14:05:56 -07:00
2020-07-08 16:35:54 -04:00

Rose - Style & Component Ember Addon for Boundary

This addon contains common styles and components shared by Boundary UIs.

Table of Contents generated with DocToc

Add Styles to an App

Add this addon to an Ember application's devDependencies as: "rose": "*", for applications included in this monorepo. Application's may then import rose styles by adding @import 'rose'; to their stylesheets.

Installation

See monorepo README for installation instructions.

Yarn Commands

List of available project commands. yarn run <command-name>

Command Description
build:development Builds the dummy app in development mode.
build Builds the dummy app for production.
lint Runs all lint commands.
lint:fix Runs automatic lint fixes for all files.
lint:hbs Lints template hbs files.
lint:hbs:fix Runs automatic lint fixes for hbs files.
lint:js Lints js files.
lint:js:fix Runs automatic lint fixes for js files.
lint:sass Lints scss files.
format Runs all auto-formatters.
format:js Auto-formats js files using Prettier.
format:hbs Auto-formats hbs files using Prettier.
format:sass Auto-formats scss files using Prettier.
start Runs the dummy app local server.
storybook Runs the Storybook local server on port 6006. Be sure to start the standard server (see above) in a separate terminal.
test Runs all tests.
test:ember-compatibility Runs tests across multiple Ember versions with ember-try.
precommit Runs all lint, format and tests.
doc:toc Automatically generates a table of contents for this README file.

Additional commands in the monorepo package may affect this projects.

Linting

  • yarn lint:hbs
  • yarn lint:js
  • yarn lint:js --fix

Formatting

Before submitting your work, be sure to run auto-formatters (see commands above). This helps to ensure consistency among authors.

  • yarn format

Building Components

To build a new component, start by generating it on the command line with ember g component rose/component-name. Then manually add a Storybook story in component-name.stories.mdx. Use the Storybook UI during component development (see Yarn commands).

Using Components

A few of the components have additional ember package dependencies that need to be installed before usage.

Component Dependency
Rose::Dropdown ember-modifier

Running tests

  • yarn test – Runs the test suite on the current Ember version
  • yarn test --server – Runs the test suite in "watch mode"
  • yarn test:all – Runs the test suite against multiple Ember versions

Running the dummy application

Contributing

See monorepo README for more contribution instructions.

Building ToC

To autogenerate a ToC (table of contents) for this README, run yarn doc:toc. Please update the ToC whenever editing the structure of README.