open-consul/ui/packages/consul-ui/app/components/flash-message
John Cowen 2200cde988
ui: Replaces almost all remaining instances of SASS variables with CSS (#11200)
From an engineers perspective, whenever specifying colors from now on we should use the form:

```
color: rgb(var(--tone-red-500));
```

Please note:

- Use rgb. This lets us do this like rgb(var(--tone-red-500) / 10%) so we can use a 10% opacity red-500 if we ever need to whilst still making use of our color tokens.
- Use --tone-colorName-000 (so the prefix tone). Previously we could use a mix of --gray-500: $gray-500 (note the left hand CSS prop and right hand SASS var) for the things we need to theme currently. As we no longer use SASS we can't do --gray-500: --gray-500, so we now do --tone-gray-500: --gray-500.

Just for clarity after that, whenever specifying a color anywhere, use rgb and --tone. There is only one reason where you might not use tone, and that is if you never want a color to be affected by a theme (for example a background shadow probably always should use --black)

There are a 2 or 3 left for the code editor, plus our custom-query values
2021-10-07 19:21:11 +01:00
..
index.scss
layout.scss
README.mdx
skin.scss

---
class: css
state: needs-love
---
# flash-message

CSS component for styling our flash messages

```hbs preview-template
<div class="flash-message">
  <p
    role="alert"
    class={{or this.type 'success'}}
  >
    <strong>
      {{capitalize (or this.type 'success')}}!
    </strong>
  </p>
</div>

<figure>
  <figcaption>Provide a widget to change the <code>class</code></figcaption>

  <select
    onchange={{action (mut this.type) value="target.value"}}
  >
    <option>success</option>
    <option>warning</option>
    <option>error</option>
    <option>exists</option>
  </select>

</figure>
```