STANDALONE API

Import

The renderer and headless notification store share one granular entry point but remain independent.

import { NeuralMessage } from '@neural-ng/core/message';

@Component({ imports: [NeuralMessage] })

Basic inline feedback

Unlike Toast, Message occupies layout space and stays exactly where it is declared.

Semantic severities

The full surface follows severity while primary and surface palettes continue to work in light and dark mode.

Filled, outlined and simple

Use filled for prominent notices, outlined for quieter panels and simple for compact field guidance.

Sizes and icons

Automatic Neural Icons can be replaced, recolored through ordinary classes or disabled.

Controlled dismissal

visible is a two-way Signal model. Closing emits one semantic event; the consumer decides when it returns.

Projected content and actions

Plain content stays in the message body. Mark controls with message-actions to keep them in the trailing action slot.

Unstyled and typed slots

Unstyled removes NeuralNg’s visual layer while semantics, model, dismissal and stable structural hooks remain.

Message, Toast and Message API

Live semantics

Error uses role="alert" and assertive announcements. Other severities use role="status" and polite announcements. Set ariaLive="off" for content already described by a field.

Dismissal

Closable messages expose a native button with a configurable accessible label. Decorative icons are hidden from assistive technology.

Motion and direction

Logical layout mirrors in RTL. Enter and leave animation durations collapse under reduced-motion preferences.

Inputs

Models and events

Typed class slots

Store type boundary

NeuralMessage is the inline component. NeuralMessageRecord is the immutable notification record exposed by NeuralMessageService. The explicit names prevent renderer and data contracts from being confused.

Component tokens