--- Title: Ant Design Component Semantic Descriptions URL: https://ant.design/llms-semantic.md --- # Ant Design 组件语义化描述 本文档包含了 Ant Design 组件库中所有组件的语义化描述信息。 > 总计 65 个组件包含语义化描述 ## 组件列表 ### alert - `root`: 根元素，包含边框、背景色、内边距、圆角、位置布局等警告提示框的基础样式 - `section`: 内容元素，采用 flex 布局控制内容区域的排版和最小宽度 - `icon`: 图标元素，包含图标的颜色、行高、外边距等样式，支持不同类型的状态图标 - `title`: 标题元素，包含标题文字的颜色、字体等样式 - `description`: 描述元素，包含描述文字的字体大小、行高等排版样式 - `actions`: 操作组元素，包含操作按钮的布局和间距样式 ### anchor - `root`: 根元素，包含布局定位、内边距、边距、背景色等基础样式 - `item`: 链接项元素，包含内边距、文字颜色、悬停状态、过渡动画等样式 - `title`: 标题文字元素，包含字体样式、颜色变化、文本装饰、过渡效果等样式 - `indicator`: 指示器元素，包含宽度、高度、背景色、位置变化、过渡动画等样式 ### badge - `root`: 根元素，包含相对定位、行内块布局、适应内容宽度等基础布局样式 - `indicator`: 指示器元素，包含定位、层级、尺寸、颜色、字体、文本对齐、背景、圆角、阴影、过渡动画等完整的徽标样式 ### breadcrumb - `root`: 根元素，包含文字颜色、字体大小、图标尺寸等基础样式，内部使用 flex 布局的有序列表 - `item`: Item 元素，包含文字颜色、链接的颜色变化、悬浮效果、内边距、圆角、高度、外边距等样式 - `separator`: 分隔符元素，包含分隔符的外边距和颜色样式 ### button - `root`: 根元素，包含边框样式、背景色、内边距、圆角、阴影效果、过渡动画、光标样式、文字权重、对齐方式等完整的按钮外观样式 - `content`: 内容元素，包装按钮文本内容，控制文本的不换行显示、居中对齐、中文字符间距优化等文本排版样式 - `icon`: 图标元素，包含图标的字体大小、颜色继承、SVG 样式重置等图标显示相关样式 ### calendar - `root`: 根元素，包含日历组件的背景色、边框、圆角等基础样式和整体布局结构 - `header`: 头部元素，包含年份选择器、月份选择器、模式切换器的布局和样式控制 - `body`: 主体元素，包含日历表格的内边距、布局控制等样式，用于容纳日历网格 - `content`: 内容元素，包含日历表格的宽度、高度等尺寸控制和表格样式 - `item`: 条目元素，包含日历单元格的背景色、边框、悬停态、选中态等交互样式 ### card - `root`: 卡片根元素，包含位置定位、背景色、边框、圆角、阴影、内边距等卡片容器的基础样式 - `header`: 卡片头部区域，包含 flex 布局、最小高度、内边距、文字颜色、字体权重、字体大小、背景色、下边框、顶部圆角等样式 - `body`: 卡片内容区域，包含内边距、字体大小等内容展示的基础样式 - `extra`: 卡片右上角的操作区域，包含额外内容的文字颜色和布局样式 - `title`: 卡片标题，包含行内块布局、flex 占比、文本省略等标题显示样式 - `actions`: 卡片底部操作组，包含 flex 布局、列表样式重置、背景色、上边框、底部圆角等操作按钮容器样式 - `cover`: 标题封面，包含封面图片的显示和布局样式 ### card:meta - `root`: 设置元信息根元素 - `section`: 设置元信息内容元素 - `avatar`: 设置元信息图标 - `title`: 设置元信息标题 - `description`: 设置元信息描述 ### checkbox - `root`: 根元素，包含行内 flex 布局、基线对齐、光标样式、重置样式等复选框容器的基础样式 - `icon`: 选中框元素，包含尺寸、方向、背景色、边框、圆角、过渡动画，以及选中状态的勾选标记样式 - `label`: 文本元素，包含文本的内边距和与复选框的间距样式 ### collapse - `root`: 根元素，包含折叠面板的边框、圆角、背景色等容器样式，控制面板的整体布局和外观 - `header`: 头部元素，包含flex布局、内边距、颜色、行高、光标样式、过渡动画等面板头部的交互和样式 - `title`: 标题元素，包含flex自适应布局、右边距等标题文字的布局和排版样式 - `body`: 内容元素，包含内边距、颜色、背景色等面板内容区域的展示样式 - `icon`: 图标元素，包含字体大小、过渡动画、旋转变换等展开收起箭头的样式和动效 ### colorPicker - `root`: 触发器容器，包含边框样式、过渡动画、尺寸控制等样式，显示颜色块和文本内容 - `popup`: - `root`: 弹出面板根容器，包含背景色、阴影效果、色彩选择面板、滑块控制和预设颜色等样式 ### datePicker - `root`: 根元素，包含相对定位、行内flex布局、内边距、边框圆角、过渡动画等日期选择器容器的基础样式 - `prefix`: 前缀元素，包含flex布局、右外边距等前缀内容的布局样式 - `input`: 输入框元素，包含相对定位、宽度、颜色、字体、行高、过渡动画等输入框的核心交互样式 - `suffix`: 后缀元素，包含flex布局、颜色、行高、指针事件、过渡动画等后缀内容的样式 - `popup`: - `header`: 弹出框头部元素，包含导航按钮、月份年份选择器等头部控制区域的布局和样式 - `body`: 弹出框主体元素，包含日期面板表格的容器布局和样式 - `content`: 弹出框内容元素，包含日期表格的宽度、边框、单元格等内容展示样式 - `item`: 弹出框单项元素，包含日期单元格的尺寸、背景色、边框圆角、悬停态、选中态等交互样式 - `footer`: 弹出框底部元素，包含确认取消按钮、快捷选择等底部操作区域的布局样式 ### descriptions - `root`: 根元素，包含描述列表容器的基础样式、重置样式、边框样式、布局方向等整体样式 - `header`: 头部元素，包含flex布局、对齐方式、下边距等头部区域的布局和样式控制 - `title`: 标题元素，包含文本省略、flex占比、颜色、字体权重、字体大小、行高等标题文字样式 - `extra`: 额外内容元素，包含左边距、颜色、字体大小等额外操作区域的样式 - `label`: 标签元素，包含颜色、字体权重、字体大小、行高、文本对齐、冒号样式等标签文字的样式 - `content`: 内容元素，包含表格单元格布局、颜色、字体大小、行高、文字换行等内容展示样式 ### divider - `root`: 根元素，包含边框顶部样式、分隔线样式等分割线容器的基础样式 - `content`: 内容元素，包含行内块显示、内边距等分割线文本内容的样式 - `rail`: 背景条元素，包含边框顶部样式等分割线连接条的样式 ### drawer - `root`: 根元素，包含固定定位、层级控制、指针事件、颜色等抽屉容器的基础样式和布局控制 - `mask`: 遮罩层元素，包含绝对定位、层级、背景色、指针事件等遮罩层的样式和交互控制 - `section`: Drawer 容器元素，包含flex布局、宽高、溢出控制、背景色、指针事件等抽屉主体的样式 - `header`: 头部元素，包含flex布局、对齐方式、内边距、字体大小、行高、下边框等头部区域的样式 - `body`: 内容元素，包含flex占比、最小尺寸、内边距、溢出滚动等内容区域的展示和布局样式 - `footer`: 底部元素，包含flex收缩、内边距、上边框等底部操作区域的样式 - `title`: 标题元素，包含flex占比、外边距、字体权重、字体大小、行高等标题文字的样式 - `extra`: 额外元素，包含flex固定布局等额外操作内容的样式控制 ### dropdown - `root`: dropdown 的根元素，设置定位、层级和容器样式 - `itemTitle`: dropdown 选项的标题内容区域，设置布局和文字样式 - `item`: dropdown 的单个选项元素，设置选项的交互状态和背景样式 - `itemContent`: dropdown 选项的主要内容区域，设置内容布局和链接样式 - `itemIcon`: dropdown 选项的图标区域，设置图标的尺寸和间距样式 ### empty - `root`: 根元素，设置文本对齐、字体和行高样式 - `image`: 图标元素，设置高度、透明度、边距和图片样式 - `description`: 描述元素，设置文本颜色样式 - `footer`: 底部元素，设置顶部边距和操作按钮样式 ### floatButton - `root`: 根元素，设置悬浮按钮的基础样式、形状尺寸、类型主题、固定定位、层级、阴影、间距等容器样式 - `content`: 内容元素，设置按钮内文字内容的字体大小、颜色、对齐、换行等文本显示样式 - `icon`: 图标元素，设置按钮内图标的尺寸、颜色、行高、对齐等图标显示样式 ### floatButtonGroup - `root`: 根元素，设置悬浮按钮组的容器样式、固定定位、层级、内边距、间距、方向模式等组合布局样式 - `list`: 列表元素，设置按钮组列表的Flex布局、圆角、阴影、动画过渡、垂直对齐等列表容器样式 - `item`: 列表项元素，设置单个悬浮按钮的样式、尺寸、形状、类型、状态、图标内容等按钮基础样式 - `itemIcon`: 列表项图标元素，设置悬浮按钮内图标的尺寸、颜色、对齐等图标显示样式 - `itemContent`: 列表项内容元素，设置悬浮按钮内文字内容、徽标、描述等内容区域样式 - `trigger`: 触发元素，设置菜单模式下触发按钮的样式、形状、图标、悬停态、展开收起状态等交互样式 - `triggerIcon`: 触发图标元素，设置触发按钮内图标的样式、旋转动画、切换状态等图标交互样式 - `triggerContent`: 触发内容元素，设置触发按钮内容区域的文字、标识、状态指示等内容样式 ### form - `root`: 根元素，包含表单项的底边距、垂直对齐、过渡动画、隐藏状态、错误警告状态等表单项容器的基础样式 - `label`: 标签元素，包含 flex 布局、溢出隐藏、文本不换行、文本对齐、垂直对齐，以及标签的颜色、字体大小、高度、必填标记等标签显示样式 - `content`: 内容元素，包含表单内容区域的布局、样式和控件容器的相关样式 ### image - `root`: 根元素，设置相对定位和行内块布局样式 - `image`: 图片元素，设置宽度、高度和垂直对齐样式 - `cover`: 悬浮图片显示的提示元素，设置绝对定位、背景色、透明度和过渡动画样式 - `popup`: - `root`: 预览根元素，设置固定定位、层级和背景遮罩样式 - `mask`: 预览遮罩元素，设置绝对定位和半透明背景样式 - `body`: 预览内容元素，设置flex布局、居中对齐和指针事件样式 - `footer`: 预览页脚元素，设置绝对定位、居中布局和底部操作区域样式 - `actions`: 预览操作组元素，设置flex布局、背景色、圆角和操作按钮样式 ### input - `root`: 根元素，包含相对定位、行内块布局、宽度、最小宽度、内边距、颜色、字体、行高、圆角、过渡动画等输入框容器的基础样式 - `input`: 输入框元素，包含输入框的核心交互样式和文本输入相关的样式 - `prefix`: 前缀的包裹元素，包含前缀内容的布局和样式 - `suffix`: 后缀的包裹元素，包含后缀内容的布局和样式 - `count`: 文字计数元素，包含字符计数显示的字体和颜色样式 ### input:password - `root`: 根元素 - `input`: 输入框元素 - `prefix`: 前缀的包裹元素 - `suffix`: 后缀的包裹元素 - `count`: 文字计数元素 ### inputNumber - `root`: 根元素，设置行内块布局、宽度、边框圆角和重置样式 - `input`: 输入框元素，设置字体、行高、文本输入和交互样式 - `prefix`: 前缀的包裹元素，设置flex布局、对齐方式和右边距样式 - `suffix`: 后缀的包裹元素，设置flex布局、边距和过渡动画样式 - `actions`: 操作元素，设置绝对定位、宽度、flex布局和数值调节按钮样式 ### inputSearch - `root`: 根元素 - `input`: 输入框元素 - `prefix`: 前缀的包裹元素 - `suffix`: 后缀的包裹元素 - `count`: 文字计数元素 - `button`: - `root`: 按钮根元素 - `icon`: 按钮图标元素 - `content`: 按钮内容元素 ### list - `extra`: 设置额外内容 - `actions`: 设置列表操作组 ### masonry - `root`: 根元素，设置相对定位、flex布局和瀑布流容器样式 - `item`: 条目元素，设置绝对定位、宽度计算、过渡动画和瀑布流项目样式 ### mentions - `root`: 根元素，设置行内flex布局、相对定位、内边距和边框样式 - `textarea`: 文本域元素，设置字体、行高、文本输入和背景样式 - `popup`: 弹出框元素，设置绝对定位、层级、背景色、圆角、阴影和下拉选项样式 ### menu - `root`: 根元素，包含菜单容器的基础样式和布局 - `item`: 条目元素，包含相对定位、块级显示、外边距、空白符处理、光标样式、过渡动画等菜单项的基础交互样式 - `itemContent`: 条目内容元素，包含菜单项内容的布局和排版样式 - `itemIcon`: 图标元素，包含最小宽度、字体大小、过渡动画、图标重置样式，以及与文本的间距控制 - `itemTitle`: 菜单标题元素(horizontal 模式不生效)，包含标题文字的样式和布局 - `list`: 菜单列表元素(horizontal 模式不生效)，包含菜单列表的布局和容器样式 - `popup`: 弹出菜单(inline 模式不生效)，包含弹出层的定位、层级、背景等样式 - `subMenu`: - `itemTitle`: 子菜单标题元素，包含子菜单标题的样式和交互效果 - `list`: 子菜单列表元素，包含子菜单列表的布局和容器样式 - `item`: 子菜单单项元素，包含子菜单项的样式和交互效果 - `itemIcon`: 子菜单条目图标元素，包含子菜单图标的尺寸和样式 - `itemContent`: 子菜单条目内容元素，包含子菜单内容的布局和排版 ### message - `root`: 根元素，设置固定定位、层级、内边距、背景色、圆角、阴影和动画样式 - `icon`: 图标元素，设置字体大小、右边距和状态颜色样式 - `content`: 内容元素，设置行内块布局、文字颜色和内容展示样式 ### modal - `root`: 根元素，包含相对定位、顶部位置、宽度、最大宽度、外边距、底部内边距等模态框容器的基础布局样式 - `mask`: 遮罩层元素，包含固定定位、层级、背景色、动画过渡等遮罩层的样式 - `wrapper`: 包裹层元素，一般用于动画容器，包含动画和过渡效果的样式 - `container`: Modal 容器元素，包含相对定位、背景色、背景裁剪、边框、圆角、阴影、指针事件、内边距等模态框主体样式 - `header`: 头部元素，包含头部内边距、下边框等头部区域样式 - `title`: 标题元素，包含外边距、颜色、字体权重、字体大小、行高、文字换行等标题文字样式 - `body`: 内容元素，包含内容区域的背景色、内边距等内容展示样式 - `footer`: 底部元素，包含底部的背景色、内边距、上边框、圆角等底部区域样式 ### notification - `root`: 根元素，设置固定定位、层级、内边距、背景色、圆角、阴影和动画样式 - `icon`: 图标元素，设置绝对定位、字体大小、行高和状态颜色样式 - `title`: 标题元素，设置颜色、字体大小、行高和外边距样式 - `description`: 描述元素，设置字体大小、颜色和外边距样式 - `actions`: 操作组元素，设置右浮动、上边距和操作按钮布局样式 ### otp - `root`: 根元素，设置行内flex布局、对齐方式、列间距和包装样式 - `input`: 输入框元素，设置文本居中、内边距和数字输入样式 - `separator`: 分隔符元素，设置OTP输入框之间的分隔符显示样式 ### pagination - `root`: 根元素，设置flex布局、对齐方式、换行和列表样式 - `item`: 页码元素，设置尺寸、内边距、边框、背景色、悬停态和激活态样式 ### popconfirm - `root`: 根元素，包含定位样式、层级控制、变换原点等基础容器样式 - `body`: 主体元素，包含内边距、背景色、圆角边框、阴影效果、背景裁剪等内容区域样式 ### popover - `root`: 根元素，设置绝对定位、层级、变换原点、箭头指向和弹层容器样式 - `body`: 内容元素，设置背景色、内边距、圆角、阴影、边框和内容展示样式 ### progress - `root`: 根元素，设置相对定位和基础容器样式 - `body`: 主体元素，设置进度条的布局和尺寸样式 - `rail`: 导轨元素，设置背景轨道的颜色和圆角样式，steps 模式下没有该元素 - `track`: 轨迹元素，设置进度填充部分的颜色和过渡动画样式 - `indicator`: 指示器元素，设置百分比文本或图标的位置和字体样式 ### qrCode - `root`: 根元素，设置flex布局、内边距、背景色、边框、圆角和相对定位样式 - `cover`: 遮罩层元素，设置绝对定位、层级、背景色和加载状态覆盖样式 ### radio - `root`: 根元素，包含布局样式、鼠标样式、禁用状态文字颜色等基础容器样式 - `icon`: 选中框元素，包含圆角样式、过渡动画、边框样式、悬停状态、焦点状态等交互样式 - `label`: 文本元素，包含内边距、文字颜色、禁用状态、对齐方式等文本样式 ### result - `root`: 根元素，包含文本对齐、布局样式等基础容器样式 - `title`: 标题元素，包含字体大小、文字颜色、行高、对齐方式等文字样式 - `subTitle`: 副标题元素，包含字体大小、文字颜色、行高等文字样式 - `body`: 内容元素，包含外边距、内边距、背景色等内容区域样式 - `extra`: 操作区域元素，包含外边距、文本对齐、内部元素间距等布局样式 - `icon`: 图标元素，包含外边距、文本对齐、字体大小、状态颜色等图标样式 ### ribbon - `root`: 根元素，设置相对定位和包装容器样式 - `indicator`: 指示器元素，设置绝对定位、内边距、背景色、圆角和缎带样式 - `content`: 文本元素，设置文本颜色和缎带内容显示样式 ### segmented - `root`: 根元素，设置行内块布局、内边距、背景色、圆角、过渡动画和容器样式 - `item`: 选项元素，设置相对定位、文本对齐、光标样式、过渡动画、选中态背景色和悬停态样式 - `icon`: 图标元素，设置图标的尺寸、颜色和与文本的间距样式 - `label`: 标签内容元素，设置最小高度、行高、内边距、文本省略和内容布局样式 ### skeleton:element - `root`: 根元素 - `content`: 内容元素 ### slider - `root`: 根元素，设置相对定位、高度、边距、内边距、光标样式和触摸事件控制 - `track`: 轨道选取条元素，设置绝对定位、背景色、圆角和过渡动画样式 - `tracks`: 多段轨道容器元素，设置绝对定位和过渡动画样式 - `rail`: 背景轨道元素，设置绝对定位、背景色、圆角和过渡动画样式 - `handle`: 滑块控制点元素，设置绝对定位、尺寸、轮廓线、用户选择、背景色、边框阴影、圆角、光标样式和过渡动画 ### space - `root`: 根元素，包含 flex 布局、间隙设置、对齐方式、换行等间距容器的基础样式 - `item`: 包裹的子组件，包含间距项的布局和样式，为每个子元素提供包装用于内联对齐 - `separator`: 分隔符，包含分隔元素的样式 ### spin - `root`: 根元素，设置绝对定位、显示控制、颜色、字体大小、文本对齐、垂直对齐、透明度和过渡动画(fullscreen 为 false 时才有效) - `indicator`: 指示器元素，设置宽度、高度、字体大小、行内块显示、过渡动画、变换原点、行高和颜色 ### spin:fullscreen - `mask`: 遮罩层元素 - `indicator`: 指示器元素 ### splitter - `root`: 根元素，设置flex布局、宽度高度、对齐方式和拉伸样式 - `panel`: 面板元素，设置flex基础值、增长比例和面板容器样式 - `dragger`: 拖拽控制元素，设置绝对定位、用户选择、层级、居中对齐、背景色、悬停态和激活态样式 ### statistic - `root`: 根元素，包含统计数值组件的重置样式和整体容器样式 - `header`: 头部元素，包含下内边距和标题区域的布局样式 - `title`: 标题元素，包含文字颜色、字体大小等标题文字的显示样式 - `content`: 内容元素，包含文字颜色、字体大小、字体族等数值内容的展示样式 - `prefix`: 前缀元素，包含行内块显示、右外边距等前缀内容的布局样式 - `suffix`: 后缀元素，包含行内块显示、左外边距等后缀内容的布局样式 ### steps - `root`: 根元素，包含 flex 布局、禁止换行、对齐方式、CSS 变量等步骤条容器的基础样式 - `item`: 步骤项元素，包含 flex 布局、相对定位等单个步骤项的基础容器样式 - `itemWrapper`: 步骤项内裹元素，包含 flex 布局、禁止换行、顶部内边距等步骤项内容的包装样式 - `itemIcon`: 步骤项图标元素，包含图标的尺寸、定位、字体大小等图标显示相关样式 - `itemHeader`: 步骤项头部元素，包含 flex 布局、禁止换行、对齐方式等头部区域的布局样式 - `itemTitle`: 步骤项标题元素，包含颜色、字体大小、行高、文字换行、过渡动画等标题文字样式 - `itemSubtitle`: 步骤项副标题元素，包含颜色、字体权重、字体大小、行高、外边距、文字换行等副标题样式 - `itemSection`: 步骤项区域元素，包含步骤项内容区域的布局和样式 - `itemContent`: 步骤项内容元素，包含颜色、字体大小、行高、文字换行、过渡动画等内容文字样式 - `itemRail`: 步骤项连接线元素，包含边框样式、边框宽度、过渡动画等连接线的样式 ### steps:items - `root`: 根元素 - `wrapper`: 步骤项内裹元素 - `icon`: 步骤项图标元素 - `header`: 步骤项头部元素 - `title`: 步骤项标题元素 - `subtitle`: 步骤项副标题元素 - `section`: 步骤项区域元素 - `content`: 步骤项内容元素 - `rail`: 步骤项连接线元素 ### switch - `root`: 根元素，包含最小宽度、高度、行高、垂直对齐、背景色、边框、圆角、光标样式、过渡动画、用户选择等开关容器的基础样式 - `content`: 内容元素，包含块级显示、溢出隐藏、圆角、高度、内边距、过渡动画等开关内容区域的布局和样式 ### table - `root`: 根元素，包含字体大小、背景色、圆角、滚动条颜色等表格容器的基础样式 - `section`: 容器元素，包含清除浮动、最大宽度、滚动条背景等表格包装容器样式 - `header`: - `wrapper`: 头部容器元素，包含表头的布局和容器样式 - `row`: 头部行元素，包含表头行的布局和样式 - `cell`: 头部单元格元素，包含相对定位、内边距、文字换行、背景色、文字颜色、字体权重等表头单元格样式 - `title`: 标题元素，包含表格标题的样式和布局 - `body`: - `wrapper`: 主体容器元素，包含表格主体的布局和容器样式 - `row`: 主体行元素，包含数据行的悬浮效果、选中状态、展开状态等交互样式 - `cell`: 主体单元格元素，包含相对定位、内边距、文字换行等数据单元格的基础样式 - `footer`: 底部元素，包含表格底部的背景色、文字颜色等样式 - `content`: 内容元素，包含表格内容区域的样式和布局 - `pagination`: - `root`: 分页根元素，包含分页组件的基础样式和布局 - `item`: 分页单项元素，包含分页项的样式和交互效果 ### tabs - `root`: 根元素，包含标签页容器的基础样式、布局和方向控制 - `item`: Item 元素，包含相对定位、内边距、颜色、文本省略、圆角、过渡动画等标签项的样式和交互效果 - `header`: 头部元素，包含标签页头部导航的布局、背景、边框等样式 - `indicator`: 指示器元素，包含指示条的颜色、位置、尺寸、过渡动画等活跃状态指示样式 - `content`: 内容元素，包含标签页内容面板的布局、内边距等内容展示样式 - `popup`: - `root`: 弹出菜单元素，包含下拉菜单的绝对定位、层级、显示控制、最大高度、滚动等样式 ### tag - `root`: 根元素，包含行内块布局、自动高度、内边距、字体大小、行高、禁止换行、背景色、边框、圆角、透明度、过渡动画、文本对齐、相对定位等标签的基础样式 - `icon`: 图标元素，包含字体大小、颜色、光标样式、过渡动画等图标的显示样式 - `content`: 内容元素，包含文本内容的颜色、字体样式等内容区域的样式 ### tag:group - `root`: 根元素，设置标签组的容器样式和布局 - `item`: 标签项元素，设置行内块显示、高度、内边距、字体大小、行高、背景色、边框、圆角、透明度、过渡动画、可选中状态等样式 ### textArea - `root`: 根元素，设置文本域包装器的样式、边框、圆角、过渡动画和状态控制 - `textarea`: 文本域元素，设置字体、行高、内边距、颜色、背景、边框、文本输入和多行文本展示样式 - `count`: 文字计数元素，设置字符计数显示的位置、字体、颜色和数值统计样式 ### timeline - `root`: 根元素，设置时间轴容器的列表样式重置、垂直布局、点状图标、轮廓样式、交替布局等基础容器样式 - `item`: 节点元素，设置单个时间节点的相对定位、外边距、内边距、字体大小、完成状态、颜色主题、布局方向等节点基础样式 - `itemWrapper`: 节点包装元素，设置时间节点内容的包装容器样式 - `itemIcon`: 节点图标元素，设置节点头部图标的绝对定位、宽高尺寸、背景色、边框、圆角、波纹动画等图标样式 - `itemHeader`: 节点头部元素，设置包含标题和连接线的头部区域布局、对齐方式、文本方向等样式 - `itemTitle`: 节点标题元素，设置节点标题文字的字体大小、行高、颜色等文本样式 - `itemSection`: 节点区域元素，设置包含头部和内容的区域容器的Flex布局、换行、间距等布局样式 - `itemContent`: 节点内容元素，设置节点详细内容的相对定位、顶部偏移、左侧外边距、文字颜色、词汇换行等内容样式 - `itemRail`: 节点连接线元素，设置连接时间节点的轨道线条的绝对定位、顶部偏移、左侧偏移、高度、边框颜色、宽度、样式等连接线样式 ### timeline:items - `root`: 根元素 - `wrapper`: 节点内裹元素 - `icon`: 节点图标元素 - `header`: 节点头部元素 - `title`: 节点标题元素 - `section`: 节点区域元素 - `content`: 节点内容元素 - `rail`: 节点连接线元素 ### tooltip - `root`: 根元素 (包含箭头、内容元素)，设置绝对定位、层级、块级显示、最大宽度、可见性、变换原点和箭头背景色 - `body`: 内容元素，设置最小宽度高度、内边距、颜色、文本对齐、背景色、圆角、阴影和边框样式 ### tour - `root`: 引导根容器，设置绝对定位、层级控制、最大宽度、可见性、箭头背景色变量、主题样式等容器样式 - `cover`: 卡片封面区域，设置文本居中对齐、内边距、图片宽度等图片展示样式 - `section`: 卡片主要内容区域，设置文本对齐、边框圆角、盒阴影、相对定位、背景色、边框、背景裁剪等卡片样式 - `footer`: 卡片底部操作区域，设置内边距、文本右对齐、边框圆角、Flex布局等底部容器样式 - `actions`: 操作按钮组容器，设置左侧自动外边距、按钮间距等按钮组布局样式 - `indicator`: 单个指示器元素，设置宽高尺寸、行内块显示、圆角、背景色、右外边距、激活状态等圆点样式 - `indicators`: 指示器组容器，设置行内块显示等指示器容器样式 - `header`: 卡片头部区域，设置内边距、宽度计算、词汇换行等头部容器样式 - `title`: 引导标题文字，设置字体粗细等标题文本样式 - `description`: 引导描述文字，设置内边距、词汇换行等描述文本样式 - `mask`: 遮罩层元素，设置固定定位、全屏覆盖、层级、指针事件、过渡动画等遮罩样式 ### transfer - `root`: 根元素，设置flex布局、穿梭框容器的基础样式和布局控制 - `section`: 区域元素，设置flex布局、宽度、高度、最小高度、边框、圆角等单侧穿梭框的容器样式 - `header`: 头部元素，设置flex布局、对齐方式、高度、内边距、颜色、背景色、下边框、圆角等头部区域的样式 - `title`: 标题元素，设置文本省略、flex占比、文本对齐、自动左边距等标题文字的布局和样式 - `body`: 内容元素，设置列表主体区域的容器样式和布局控制 - `list`: 列表元素，设置列表内容的样式、布局和滚动控制 - `item`: 列表项元素，设置相对定位、内边距、边框、悬停态、选中态、禁用态等列表项的交互样式 - `itemIcon`: 列表项图标元素，设置复选框等图标的样式和交互状态 - `itemContent`: 列表项内容元素，设置文本省略、内边距等列表项文本内容的展示样式 - `footer`: 页脚元素，设置底部操作区域的样式和布局 - `actions`: 操作元素，设置穿梭按钮组的样式、布局和交互状态 ### tree - `root`: 根元素，设置树形控件的基础样式、布局和容器控制 - `item`: 条目元素，设置树节点的基础样式、拖拽状态、角色属性、缩进、切换器、内容包装器等节点结构 - `itemTitle`: 标题元素，设置树节点标题文字的显示样式和文本内容 - `itemIcon`: 图标元素，设置树节点图标的样式、尺寸和状态显示 ### treeSelect - `root`: 根元素，设置树选择器的基础样式、边框、圆角容器样式 - `prefix`: 前缀元素，设置前缀内容的布局和样式 - `input`: 输入框元素，设置文本输入、搜索、选择值显示等输入框的核心交互样式 - `suffix`: 后缀元素，设置后缀内容、清除按钮、下拉箭头等后缀区域的样式 - `popup`: - `item`: 弹出菜单条目元素，设置树节点选项的样式、悬停态、选中态等交互状态 - `itemTitle`: 弹出菜单标题元素，设置树节点标题文字的显示样式 - `root`: 弹出菜单元素，设置下拉树形选择面板的定位、层级、背景、边框、阴影等弹层样式 ### upload - `root`: 根元素容器，包含布局样式、禁用状态文字颜色、用户选择控制、鼠标样式等基础样式 - `list`: 文件列表容器，包含布局排列、过渡动画、间距控制等样式 - `item`: 文件项元素，包含内边距、背景色、边框样式、悬停效果、状态颜色、过渡动画等样式 --- Title: Resources URL: https://ant.design/docs/resources --- ## Design Resources Please find below some of the design resources and tools about Ant Design that we consider valuable. More of this is still being collected. You can leave feedback about Sketch Symbols [here](https://www.yuque.com/kitchen/topics/216).
- Sketch Symbols - https://gw.alipayobjects.com/zos/basement_prod/048ee28f-2c80-4d15-9aa3-4f5ddac50465.svg - Sketch Symbols for Desktop - https://github.com/ant-design/ant-design/releases/download/5.13.3/AntDesign5.0_UI.KIT_202401.sketch - Official - Mobile Components - https://gw.alipayobjects.com/zos/basement_prod/c0c3852c-d245-4330-886b-cb02ef49eb6d.svg - Sketch Symbols File for Mobile - https://gw.alipayobjects.com/os/bmw-prod/d6266aef-25b7-4892-b275-ce214121831c.sketch - Official - Ant Design Pro - https://gw.alipayobjects.com/zos/basement_prod/5edc7f4d-3302-4710-963b-7b6c77ea8d06.svg - Common Templates and Pages - https://gw.alipayobjects.com/os/bmw-prod/22208f9d-f8c5-4d7c-b87a-fec290e96527.sketch - Official - Ant Design Chart - https://gw.alipayobjects.com/zos/basement_prod/a9dc586a-fe0a-4c7d-ab4f-f5ed779b963d.svg - Sketch Symbols for Chart - https://gw.alipayobjects.com/os/bmw-prod/704968a5-2641-484e-9f65-c2735b2c0287.sketch - Official - Kitchen - https://gw.alipayobjects.com/zos/basement_prod/d475d063-2754-4442-b9db-5d164e06acc9.svg - A Sketch plugin collection - http://kitchen.alipay.com - Official - Ant Design Landing - https://gw.alipayobjects.com/zos/basement_prod/b443f4be-5116-49b7-873f-a7c8502b8f0e.svg - Landing Templates - https://landing.ant.design/docs/download-cn - Official - Figma Resources - https://gw.alipayobjects.com/zos/basement_prod/7b9ed3f2-6f05-4ddb-bac3-d55feb71e0ac.svg - Always up-to-date Ant Design Figma resources - https://www.antforfigma.com - Figma Open Source Library - https://gw.alipayobjects.com/zos/basement_prod/7b9ed3f2-6f05-4ddb-bac3-d55feb71e0ac.svg - Free open source Figma library with complete accurate to code components - https://www.figma.com/community/file/831698976089873405 - AntBlocks UI for Figma - https://uploads-ssl.webflow.com/64dc925e7cb893427a5c9cdc/64e4610f7818dcc7501057ad_antblocks-ui-card-img.svg - High-quality, responsive, and customizable React components built on Ant Design - https://www.antblocksui.com/#figma - Ruyi Design Assistant - https://github.com/ant-design/ant-design/assets/507615/45201521-37d0-4360-b81e-a1260dedad7a - Figma Plugin,Design using Antd code component library and deliver component code that is friendly to developers - https://www.figma.com/community/plugin/1192146318523533547 - UI Kit for Adobe XD - https://uploads-ssl.webflow.com/5ecbd337fe499992c9ed75ba/5f2a7a30f3e817085cec5ac9_ant-xd-svg.svg - Library of components for Desktop - https://www.antforxd.com - MockingBot - https://cdn.modao.cc/logo_mockingbot.svg - Rich component resources - https://modao.cc/square/ant-design - JiShi Design - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*dxzdQYWlmjMAAAAAAAAAAAAAARQnAQ - Use full components and templates from JiShi Design - https://js.design/antd - MasterGo - https://mastergo-local-default.oss-cn-beijing.aliyuncs.com/ant-design-mastergo.svg - Use full components and templates from MasterGo - https://mastergo.com/community/?utm_source=antdesign&utm_medium=link&utm_campaign=resource&cata_name=AntDesign - Ant for Plasmic - https://user-images.githubusercontent.com/7129/149994038-76214796-cd6a-4e80-b0a4-117e8edac050.png - Drag/drop live Ant components and manipulate props in this React visual builder - https://www.plasmic.app/ant-design ## Articles Do you want to know the story behind the Ant Design design system? How can I better apply Ant Design? You can check out our well selected articles below. You are also welcome to follow [Ant Design Official Column](https://www.zhihu.com/column/c_1310524851418480640). There you will find the latest sharings and discussions related to the Ant Design design system, such as Ant Design, AntV visualization, Kitchen design Plug-ins, B-side product design, SaaS product design, natural interaction, growth design, intelligent design, design engineering, etc. ## Reference Please find below the books that inspired us, saved our time and helped us to overcome difficulties when designing components and patterns. If you want to know more about UI design, we recommend you these awesome design systems: [Fiori Design](https://experience.sap.com/fiori-design-web/), [Human Interface Guidelines](https://developer.apple.com/ios/human-interface-guidelines/), [Lightning Design System](https://lightningdesignsystem.com/getting-started/), [Material Design](https://material.io/).
- About Face 4 #C7EBD6 - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*GA-CRIRqKjgAAAAAAAAAAABkARQnAQ - The Interactive Design Guide for Digital Products and System - https://www.wiley.com/en-sg/About+Face%3A+The+Essentials+of+Interaction+Design%2C+4th+Edition-p-9781118766576 - Designing Web Interfaces #009C94 - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*KK2xSJu0M80AAAAAAAAAAABkARQnAQ - Best Practice, Patterns and Principles for Web Interface - http://shop.oreilly.com/product/9780596516253.do - Designing Interfaces #9489CF - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*slN2QpTvIs0AAAAAAAAAAABkARQnAQ - Interface Design Guidelines - https://www.amazon.com/Designing-Interfaces-Patterns-Effective-Interaction/dp/1449379702/ref=pd_sbs_14_t_1/131-2623973-6077764?_encoding=UTF8&pd_rd_i=1449379702&pd_rd_r=ebe12a8d-435f-474b-a593-72aadf26c45a&pd_rd_w=18rob&pd_rd_wg=bhRFl&pf_rd_p=5cfcfe89-300f-47d2-b1ad-a4e27203a02a&pf_rd_r=8V8CD0EE336ZZEG15DEN&psc=1&refRID=8V8CD0EE336ZZEG15DEN - Non-Designer's Design Book, The, 4th Edition #FAF0CD - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*1HbNSIju7pEAAAAAAAAAAABkARQnAQ - Basic Principles of Good Design - http://www.peachpit.com/store/non-designers-design-book-9780133966152 - The Design of Everyday Things #F8F3D1 - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*4woBSLvOjfMAAAAAAAAAAABkARQnAQ - About the People-oriented Design Philosophy - https://jnd.org/the-design-of-everyday-things-revised-and-expanded-edition/ - Emotional Design #E8EEB4 - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*6ZQJQoKRORsAAAAAAAAAAABkARQnAQ - Explain the Role of Emotional Factors in Design - https://www.amazon.com/Emotional-Design-Love-Everyday-Things/dp/0465051367 - Web Form Design #C2DAED - https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*VhhwRo7axKQAAAAAAAAAAABkARQnAQ - The Essence of Form Design - https://rosenfeldmedia.com/books/web-form-design/ --- Title: Visualization Page URL: https://ant.design/docs/spec/visualization-page --- Data visualization templates depict information and assist users to understand the data, by displaying a series of multiple charts. By viewing and interacting with the charts, users can analyze the data and eventually create data-driven strategies. ## Design Goals To help users quickly and clearly understand the meaning of data, analyze trends and make decisions. --- ## Design Principles

Organized

Define the layout logically, sort the content by priority. In most cases, in order to emphasize the common-used analysis thoughts, you should organize the information from top to bottom and from left to right, or use progressive interactions. To sum up, put the summary first, then focus on filters, and finally provide details whenever the user needs.

Focused

Put the most important charts and the key scorecards on the top or upper part the page.

Accurate

Keep data accurate, clear and complete.
1. Use the correct chart type.
2. Provide explanations where necessary.

### Do’s & Don’ts Do Don't When the data is highly aggregated, add details to your chart.
Do Try to highlight the primary information by placing it first on a screen. Limit the sum of modules to 5-9 to avoid information overload.
Do Make good use of filtering capability. Let users observe the overview and check the detailed data at the same time. This way users can explore data quickly whenever they have questions. [text](vscode-file://vscode-app/Applications/VSCodium.app/Contents/Resources/app/out/vs/code/electron-sandbox/workbench/workbench.html) ## Typical Templates ### Presentation Dashboards In order to help users make decisions, tile the most critical data from the overall perspective on the whole page. When all of the indicators share similar importance, choose the layout on the left; to emphasize one of them, select the one on the right. #### Indicator Dashboards **When to use** When decision-makers need an overview and the option to gain further insights via drill-down. **Related capabilities** Key indicator, scorecard, filter, chart. #### [Monitor Dashboards](https://preview.pro.ant.design/dashboard/monitor) **When to use** This type of dashboard provides an overview of the data for decision making. Usually there is a central topic, around which presents multi-dimension indicators, helping the users find out abnormal immediately. **Related capabilities** Key indicator, scorecard, chart, map. ### Analytics Dashboards Analytics dashboards separate the data-analysis interface into several parts. Usually their layouts are "summary and description" structure, showing overviews of the whole information with different aspects. These dashboards can assist the users to discover the current problems. #### Multi-dimension Analytics Dashboards **When to use** To analyze multiple dimension of data, surround the same topic. **Related capabilities** Key indicator, scorecard, filter, chart. ### Detail Templates Detail templates display the overview and detailed information of a report or a unique indicator. Users can set texts, lists and charts according to their business needs. #### Data Details **When to use** To show the details of the reports. **Related capabilities** Filter, chart, table. ### Design Suggestions #### Connect Analysis Steps - Figure out users’ roles and aims, and choose the categories of template accordingly. Different business roles pay attention to different key data. There are two common-used types of indicators: high-level dashboard data, and detailed information. - Decision-makers can select templates which describe the results; - Operators can choose templates which provide more analysis capabilities and detailed information. - Confirm the priority of the key indicators, and then define the page layouts accordingly. Put the most important data on the most outstanding positions. - Please remember, you can connect the user interfaces through interactive modes, telling your own stories.
#### Combination Methods of Cards 1. One card, one topic.
2. Place closely-related datasets on one card, and use split lines to break it into different areas. #### Use Suitable Charts After designing the draft layout, select related visualization charts based on how summarized or detailed the data is. Usually scorecards and ranking lists are used for information summaries, tables and texts express details, and charts are between the two categories. #### Color Palette ## Read more ### Relative Rules - [AntV Visualizatio Design Principles](https://www.yuque.com/mo-college/vis-design/pwh679) - [AntV Visualization Color Palette](https://www.yuque.com/mo-college/vis-design/ugbofr) - [AntV Visualization Interaction Design Guidelines](https://www.yuque.com/mo-college/vis-design/yygtlg) ### Relative Modules or Components - [AntV Chart Samples](https://g2plot.antv.vision/en/examples/gallery) --- Title: Visualization URL: https://ant.design/docs/spec/visual --- The visual language is based on a set of design guidelines with data visualization features derived from the intermediate design language Ant Design, which makes the data expression more in line with the user's psychology, helping the “designer” to incubate visual solutions with more business characteristics to meet the individualization. Design requirements, shielding unnecessary design differences and implementation costs, thus liberating the "designer" and front-end R&D resources, and achieving comprehensive improvement of data chart development efficiency. At the same time, this is a dynamically updated design document, your reading and feedback is the driving force for us to continue to advance, here is our [GitHub feedback url](https://github.com/antvis/site/issues). ## Design Resources We provide comprehensive design principles & guidelines and design resource files (Sketch), as well as a complete graphical usage note to help users quickly understand charts and design high quality visualization charts. - [Design Principles](https://antv.vision/zh/docs/specification/principles/basic) - [Design Resources](https://antv.vision/zh/docs/specification/resources) - [Charts Usage](https://antv-2018.alipay.com/zh-cn/vis/chart/index.html) ## Front end implementation We encapsulate a set of AntV component libraries based on native JavaScript, which includes a high-interaction base chart library G2Plot, a chart library G6 focusing on process and relationship analysis, a chart library F2 for mobile applications, and other frameworks in the community. - [G2: Grammar of Graphics](https://g2.antv.vision/en) - [G2Plot: a charting library](https://g2plot.antv.vision/en) 🔥 - [G6: Graph Visualization Framework](https://g6.antv.vision/en) - [F2: Mobile Charts](https://f2.antv.vision/en) - [L7: Geospatial Visualization Analysis](https://l7.antv.vision/en) - [React AntV](https://charts.ant.design/en) ## How to Design ### Understanding the users Who are the users? What information do they want to get from the visualisations? In an enterprise product, users may be company executives, BI analysts, operations, data developers, and other different roles. Different roles may use visualisations for different purposes and in different ways. It is recommended to fully profile the users before starting the design in order to tell your data story completely and present your data insights accurately. ### Design Principles - Accuracy: The conversion of data into visual representations that do not distort, mislead or omit, and that faithfully reflect the information contained in the data; - Effective: Information is conveyed in a focused manner, with restraint and without redundancy, avoiding information overload, and using the most appropriate amount of Data-ink Ratio (Data-ink Ratio) to express the most useful information to the user; - Clarity: The presentation is clear, easy to read and organised, which helps users to reach their goals quickly and get more information in the least amount of time; - Aesthetics: perfect expression of the data, reasonable use of visual elements for artistic creation, without excessive modification, to give users an elegant experience. ## Chart usage ### Choosing the right chart type We provide a complete description of chart usage to help you choose chart types more wisely. #### Time series Typically used to show trends and changes in data in the time dimension. #### Comparison Uses the length, width, position, area, angle and colour of a graph to compare the magnitude of values and is often used to show comparisons of values between different classifications. #### Distribution Typically used to show the distribution of values on continuous data. #### Process Typically used to represent process flow, flow relationships. #### Proportion Shows the percentage relationship on the same dimension. For more chart usage content, go to [AntV Chart usage](https://antv-2018.alipay.com/zh-cn/vis/chart/index.html) ### Colour Swatches AntV provides a default set of chart colours, including colour usage.For more colour swatches, go to [AntV - Design language - Vision](https://antv.vision/specification/language/palette) ### Component Usage Recommendations #### Title and Notes The title is a paragraph that elaborates on the subject of the chart; the notes indicate the source of the data and make the chart appear to be from a clear and reliable source. #### Axle Used to define the mapping relationship between data in a coordinate system in terms of direction and value. #### Legend Used to explain the meaning of all visual elements contained in the chart area. #### Labels Content annotation for the current set of data. #### Alerts Message This means that when the mouse hovers over the chart or the finger clicks on a data point of the mobile device, the data of the point is displayed in the form of interactive prompts, such as the value of the point, the unit of the data, etc. #### Graphics The graph is the visual presentation of the visual channels of the statistical chart mapped on the shape and is the main part of the chart, the other chart components are intended to help the reader to better understand the relationship of the data mapped on the graph. For suggestions on how to use the components, go to [AntV - Design language - Component Design Guidelines](https://antv.vision/zh/docs/specification/components/titlenotes) ### Chart layout adaptation Data visualisation is always facing the conflict between massive data volume and limited screen space, how to solve the problem of adapting the content to different ends and different screen sizes, and help users understand the information and analyse the insights faster in the limited space is the problem we have been committed to research. In Ant Design's visualisation system, we have developed a set of layout adaptation rules for full-volume charts, sorting out a layout adaptation system that applies to all charts, from the overall chart, to the atomic components within the chart. Take the moving image on the right as an example, where the axis labels of the horizontal axis are rotated to follow the specific dimensions. More content will be released soon, stay tuned. ### Interaction dynamic interaction Different from the relatively static presentation of traditional data reports, interactive charts do not stop at the level of information display. Users continuously interact with the charts to get deeper analysis and information from the data. In data visualisation, we break down the interaction actions into three layers, namely "data acquisition", "information processing" and "knowledge flow", according to the user's level of consciousness and the goals corresponding to each level. It matches the motto of "overview first, focus on filtering, and then view the details as needed" in visual information retrieval. It is also in line with the basic logic of human seeking information: first general, then local, and then focus on the point of interest to explore, which is a process from the surface to the inside. For more interactive charts go to [AntV - Design language - Interaction](https://antv.vision/zh/docs/specification/language/interact) --- Title: Design Values URL: https://ant.design/docs/spec/values --- The design values of Ant Design provide designers with internal standards for evaluation, enlighten and inspire the design principles and design patterns, and then offer guidance and general solutions for specific design problems.
General
Here are four design values of Ant Design: ## Natural
Natural
The light-speed iteration of the digital world makes products more complex. However, human consciousness and attention resources are limited. Facing this design contradiction, the pursuit of natural interaction will be the consistent direction of Ant Design. - **Natural user cognition**: According to cognitive psychology, about 80% of external information is obtained through visual channels. The most important visual elements in the interface design, including layout, colors, illustrations, icons, etc., should fully absorb the laws of nature, thereby reducing the user's cognitive cost and bringing authentic and smooth feelings. In some scenarios, opportunely adding other sensory channels such as hearing, touch can create a richer and more natural product experience. - **Natural user behavior**: In the interaction with the system, the designer should fully understand the relationship between users, system roles, and task objectives, and also contextually organize system functions and services. At the same time, a series of methods such as behavior analysis, artificial intelligence and sensors could be applied to assist users to make effective decisions and reduce extra operations of users, to save users' mental and physical resources and make human-computer interaction more natural. > To get to know the past and present of natural values, [please move to the column](https://zhuanlan.zhihu.com/p/44809866). ## Certain
Certain
Interfaces are the medium of interaction between users and the system. They are the means rather than the purpose. Based on the pursuit of "natural" interaction, the product interfaces created by Ant Design should be high certainty and low cooperative entropy. - **Designer certainty**: Enterprise products are made by collaboration. The more participants, the higher the entropy of cooperation. This is why low-efficiency design and difficult maintenance of the product system exists. By exploring the design rules and modular design ideas, designers should be provided with simplified design rules, components and patterns so they can reduce the cooperative entropy and a more efficient design process. - **Keep restraint**: Don't make a decision before you figure it out. Designers should focus on the most valuable product features using minimal design elements to express. As Antoine de St. Exupery said: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." - **Object-oriented**: Explore design rules and abstract them as "objects" to enhance the flexibility and maintainability of user interface design, while reducing the designer's subjective judgment and uncertainty of the system. For example, color value conversion and spacing typesetting. - **Modular design**: Encapsulating the complex or reusable parts could provide limited interfaces to interact with other modules, ultimately reducing overall system complexity, thereby improving reliability and maintainability. Designers can use existing resources or abstract their reusable resources to save the unnecessary and low additional design to keep their focus on where creativity is most needed. - **User certainty**: User's daily work is completed through the collaboration of enterprise products. In addition to considering the consistency of a single product design, good certainty is required to be maintained across products, terminals, and systems. Consistent appearance and interaction, maintaining a familiarity to user, can reduce the difficulty of learning, cognitive and operating costs, and improve work efficiency. ## Meaningful
Meaningful
A product or function is created by a designer not because of the designer's needs, but to carry a user's work mission. Product design should be user-centered to promote the achievement of the user's mission. Simultaneously, based on "nature" and "certainty" design values, we should regard user's human needs and create meaningful human-computer interaction for the work process. - **Meaning of result**: Clear goals, immediate feedback. Understand the objectives, clearly disassemble the sub-objectives according to the use process, and let each interaction revolve around the achievement of the main objectives. Provide appropriate and immediate feedback for each action, so that users can understand the operation results. Besides, emotional design can be used to pacify users' negative emotions and enhance users' positive emotions. - **Meaning of process**: Moderate challenge, full devotion. Adjust the difficulty of work in different scenarios, make the function trigger at the right time to match the user's skill. If not necessary, do not add entities. Do not distract users, let users focus on task achievement, rather than the interface. Let the current work be neither to simple nor too complex. The challenges are moderate, but higher challenges are raised as the user's capabilities grow. It allows users to continue to immerse themselves in the flow of work and gain fulfilling work experience. ## Growing
Growing
The growth of enterprise product's capabilities is accompanied by the evolution of user system roles. Designers should be responsible for the products they create and improve the discoverability of functions and values. Designers should design with the vision of development and consider the common growth of both ends of humans and computers. - **Value connection**: The growth of products depends on the expansion and deep use of users, while the growth of users depends on the growth of product functions. Designers should establish system design thinking, understand the value of product functions, explore user needs in different scenarios, and establish a connection between value and needs. Let product value be discovered and help users build more effective and efficient ways of working. - **Man-Computer Symbiosis**: More connections between product functions and user requirements make human-computer interaction closer and users and system are growing together. When designing products, users and systems should not be separated from each other. They should be considered as a dynamic group to ensure that they are flexible, inclusive and full of vitality. --- Title: Use Transition URL: https://ant.design/docs/spec/transition --- Our Gray Matter are wired to react to dynamic things like movement, shape change and color change. Transitions smooth out the jarring world of the Web, making changes appear more natural. The main purpose for Transitions is to provide an engaging interface and reinforce communication. - Adding: The added elements should inform the users how to use, and the modified elements should be recognized. - Receding: The irrelevant page elements should be removed properly. - Normal: The elements without any change on the page can be safely ignored. --- ## Maintain Context While Changing Views Slide In and Slide Out: Create an illusion of virtual space.
Carousel: Carousels are great for extending virtual space.
Accordion: Accordion helps maintain context while switching views.
--- ## Explain What Just Happened Adding an Object: Add an object in the table or chart.
Deleting an Object: Delete an object in the table or chart.
Modifying an Object: Modify an object in the table or chart.
Calling out an Object: Click the page element and call out a new object. --- ## Improve Perceived Performance If actual performance can hardly improved, there is a difference between actual performance and perceived performance. Diverting the user's attention is a good way to improve the perceived time an operation takes. --- ## Natural Motion Please refer to [Ant Motion, a motion language](https://motion.ant.design/language/basic). --- Title: Stay on the Page URL: https://ant.design/docs/spec/stay --- Solve most of problems on the same page and avoid a new one, because the page refresh and forwarding can lead to change blindness, in addition to disrupting the user's mental flow. > **Change Blindness** is a surprising perceptual phenomenon that occurs when a change in a visual stimulus is introduced and the observer does not notice it. People's poor ability to detect changes has been argued to reflect fundamental limitations of human attention, from the term of Change blindness, Wikipedia. > **Flow**, also known as the zone, is the mental state of operation in which a person performing an activity is fully immersed in a feeling of energized focus, full involvement, and enjoyment in the process of the activity, from the term of Flow, Wikipedia --- ## Overlays good example good example (special case) bad example
example of Detail Overlay
example of Input Overlay
--- ## Inlays example of List Inlay
example of Tabs
--- ## Virtual Pages In the process of interaction design, Overlays allow you to bring additional interactions or content in a layer above the current page. Inlays allow you to do this within the page itself. However, another powerful approach to keeping users engaged on the current page is to create a virtual page. That is to say, we create the illusion of a larger virtual page.
--- ## Process Flows It has long been common practice on the Web to turn each step into a separate page. While this may be the simplest way break down the problem, it may not lead to the best solution. For some Process Flows it makes sense to keep the user on the same page throughout the process.
example of Responsive Disclosure
example of Configurator Process
example of Dialog Overlay Process --- Title: Shadow URL: https://ant.design/docs/spec/shadow --- Shadow originates from the physical phenomenon of reflecting the distance between objects in real life. For the user interface (UI), we often simulate this through element projection to inform the user about the height distance and layer hierarchy between elements. ## Height Shadows are produced by two surfaces at different levels, and the intensity is determined by the distance between them. Therefore, the height of an object directly affects its shadow. The farther an object is from the ground, the larger and blurrier the shadow becomes. We will divide the system into four UI levels: none, low, medium, and high, each distributed across different height levels, with varying shadow properties.
height levels
**Layer 0**: When an object is close to the ground, its shadow overlaps completely with the object itself. In the UI, no shadow value is defined for this layer. For example: input boxes.
height layer 0
**Layer 1**: When an object appears at the low level, it enters a floating state when manipulated (hovered, clicked, etc). Once the operation is completed or canceled, the hover state feedback disappears, and the object returns to its original level. For example: card hovering.
height layer 1
**Layer 2**: When an object appears at the medium level, it expands and follows the relationship with the reference layer. The object opens from elements on the ground and moves with the movement of the elements at that level. For example: dropdown panels.
height layer 2
**Layer 3**: When an object appears at the high level, its movement is independent of other levels. For example: dialog boxes.
height layer 3
## Light Source The direction of a shadow is determined by the relative position of the light source and the object. Assuming the height of the light source remains constant, the distance between the light source and the object, as well as the distance between the object and the shadow, are directly proportional. The further away the light source, the further away the shadow from the object. In the UI, the direction of shadows is typically represented using the `X, Y` coordinates.
light source
## Shadow Values As mentioned above, shadows are generated by illumination. The main factors affecting their values are the height of the object and the position of the light source: 1. At different heights, the shadow's color, blur, and area vary. Objects further from the ground produce lighter shadows with higher blur and larger area, while those closer to the ground create darker shadows with lower blur and smaller area. 2. The direction of the projection is primarily determined by the relative position of the light source and the object. In Ant Design, different shadow directions are used in various contexts: - Downwards Shadow: mainly used inside components or the components themselves, which is the most common use case. - Upwards Shadow: mainly applied to bottom navigation or toolbars, etc. - Leftwards Shadow: mainly used in right-side navigation bars, drawer components, or fixed table headers. - Rightwards Shadow: mainly used in left-side navigation bars, drawer components, or fixed table headers. Shadow simulates real-world feedback. To make shadows more realistic, Ant Design adopted a three-layer shadow expression method in version 4.0, making shadows softer and more realistic.
shadow value
### Common Shadow Usage Design Table **Layer One:**
Shadow Type Shadow Color (rgba) Direction (X, Y) Blur Spread
@shadow-1-up rgba(0, 0, 0, 0.16) 0px, -1px 2px -2px
rgba(0, 0, 0, 0.12) 0px, -3px 6px 0px
rgba(0, 0, 0, 0.09) 0px, -5px 12px 4px
@shadow-1-down rgba(0, 0, 0, 0.16) 0px, 1px 2px -2px
rgba(0, 0, 0, 0.12) 0px, 3px 6px 0px
rgba(0, 0, 0, 0.09) 0px, 5px 12px 4px
@shadow-1-left rgba(0, 0, 0, 0.16) -1px, 0px 2px -2px
rgba(0, 0, 0, 0.12) -3px, 0px 6px 0px
rgba(0, 0, 0, 0.09) -5px, 0px 12px 4px
@shadow-1-right rgba(0, 0, 0, 0.16) 1px, 0px 2px -2px
rgba(0, 0, 0, 0.12) 3px, 0px 6px 0px
rgba(0, 0, 0, 0.09) 5px, 0px 12px 4px
**Layer Two:**
Shadow Type Shadow Color (rgba) Direction (X, Y) Blur Spread
@shadow-2-up rgba(0, 0, 0, 0.12) 0px, -3px 6px -4px
rgba(0, 0, 0, 0.08) 0px, -6px 16px 0px
rgba(0, 0, 0, 0.05) 0px, -9px 28px 8px
@shadow-2-down rgba(0, 0, 0, 0.12) 0px, 3px 6px -4px
rgba(0, 0, 0, 0.08) 0px, 6px 16px 0px
rgba(0, 0, 0, 0.05) 0px, 9px 28px 8px
@shadow-2-left rgba(0, 0, 0, 0.12) -3px, 0px 6px -4px
rgba(0, 0, 0, 0.08) -6px, 0px 16px 0px
rgba(0, 0, 0, 0.05) -9px, 0px 28px 8px
@shadow-2-right rgba(0, 0, 0, 0.12) 3px, 0px 6px -4px
rgba(0, 0, 0, 0.08) 6px, 0px 16px 0px
rgba(0, 0, 0, 0.05) 9px, 0px 28px 8px
**Layer Three:**
Shadow Type Shadow Color (rgba) Direction (X, Y) Blur Spread
@shadow-3-up rgba(0, 0, 0, 0.08) 0px, -6px 16px -8px
rgba(0, 0, 0, 0.05) 0px, -9px 28px 0px
rgba(0, 0, 0, 0.03) 0px, -12px 48px 16px
@shadow-3-down rgba(0, 0, 0, 0.08) 0px, 6px 16px -8px
rgba(0, 0, 0, 0.05) 0px, 9px 28px 0px
rgba(0, 0, 0, 0.03) 0px, 12px 48px 16px
@shadow-3-left rgba(0, 0, 0, 0.08) -6px, 0px 16px -8px
rgba(0, 0, 0, 0.05) -9px, 0px 28px 0px
rgba(0, 0, 0, 0.03) -12px, 0px 48px 16px
@shadow-3-right rgba(0, 0, 0, 0.08) 6px, 0px 16px -8px
rgba(0, 0, 0, 0.05) 9px, 0px 28px 0px
rgba(0, 0, 0, 0.03) 12px, 0px 48px 16px
--- Title: Workbench URL: https://ant.design/docs/spec/research-workbench --- The workbench is often used as the homepage of an application, providing a convenient hub for users. It offers common information entry points, navigating to various functional modules of the application in a hub-and-spoke manner; it presents information that the user currently needs to focus on, shortening the path to key information; and allows users to directly perform some high-frequency tasks on the workbench. --- ## Design Goals User-side: Provide shortcuts for handling and viewing information and necessary help for users;
Product-side: Communicate better with users, appropriately promote new trends and operational content of the product. ## Design Principles

Findability

Can users locate the information they want?

Reduce Memory Load

Understand the core goals of users returning to the site and provide the shortest navigation paths to possible destinations.

## How to Design #### Template - Workbench **When to Use** - Shorten the navigation path for users returning to the site; - Provide common navigation entry points for users. **Involved Functions** Help; Core Data; Shortcuts; To-Do List; Focus; Operational Modules. **Design Suggestions** - Display modules related to daily work, keeping the total number of modules between 5-9; - Present the most frequently used content on the first screen whenever possible; - Provide role-based differentiated views. #### Template - New User Guide **When to Use** - When new users arrive at the platform and have not yet started any work, shorten the learning time for new users; - When some modules have no content, refer to the "Empty State" guidelines. **Involved Functions** Help; Empty State Guide. **Design Suggestions** - Introduce the platform's purpose to users and guide them to start working; - If users need to manage complex objects, provide a Demo preview entry; ### Design Suggestions #### Choose the Right Navigation Method This type of page generally provides two types of navigation forms.
① Users know the function they want to use and need to navigate to it. For example:
② Discovery navigation, where users need to complete a task but do not know which function to use. For example:
#### Arrange Content by Usage Frequency Arrange the content based on usage frequency in the daily work. #### Consider Error States See Error Page > Additionally, whether to recommend personalized customization for users is still under exploration. --- Title: Result Page URL: https://ant.design/docs/spec/research-result --- A result page is a page that provides feedback on the outcome of an operation. It is the strongest form of feedback mode. ## When to Use When an operation process is completed and clear feedback is needed for the user, such as the final step of a step form.
When a large amount of information needs to be displayed on the result page. ## Design Goals Convey the task completion result to the user, guide the user to the next operation, and establish the user's trust in the system through effective feedback. ## Design Principles

Use Cautiously

The result page is a heavy feedback method, only suitable for scenarios where strong user attention is needed, the information volume is large, and the page stays permanently. It is not recommended for other scenarios.

End Instantly

When the result status is successful, it can automatically jump after a few seconds (3-5 seconds is recommended).

Simplify Information

The information on the result page should be the result triggered by the submission action, such as validation should be completed in the form. The information on the result page should be concise, only displaying result-related content. Additional information can be added for special scenarios.

## Design Suggestions Correct Example Incorrect Example Correct Example Incorrect Example The title should be constructed as "Object + Action + Result/Status" or "Action + Result/Status".
Correct Example Incorrect Example It is recommended to limit the guidance operations to no more than 2 items, as too many operations can cause confusion for users.
Correct Example For lighter feedback, it is not recommended to use a result page. Use global tips, warning tips, notification boxes, etc. Refer to feedback design guidelines for details.
Correct Example If the result status is successful, inform the user that it will automatically jump after a few seconds on the main button. ## How to Design ### Basic Layout The result page can provide the following content: 1. Result Feedback: Clearly inform the user of the submission result; 2. Result Explanation (optional): Used for brief explanations of the result if needed; 3. Suggested Actions: Guide the user to continue with subsequent tasks; 4. Additional Information (optional): Provide supplementary information to the user along with the result; marketing modules. #### Template - Basic Result Page Displays the result status and guides the user to the next operation. #### Template - Complex Result Page In addition to basic information like result status and guidance operations, it also displays related recommendations, process progress, error details, etc. #### Additional Information Types ## Further Reading ### Relevant Global Rules - [Feedback](/docs/spec/research-message-and-feedback) ### Relevant Modules or Components - [Form Page](/components/form-cn/) ### External Reference Articles - [Fiori Message Feedback Component Rules](https://experience.sap.com/fiori-design-web/message-box/) - [Aliyun Result Page Design](https://xconsole.aliyun-inc.com/scenes/resultpage) - [CANVAS Message Feedback Component Rules](https://canvas.hubspot.com/components/alerts-messaging) - [PREDIX Notification and Alert Component Rules](https://www.predix-ui.com/#/design/communication/notifications) --- Title: Design Patterns (Research) URL: https://ant.design/docs/spec/research-overview --- In the Exploration channel, we will publicly share the design patterns we are researching and improving, as well as unfinished content. Most of the content can be built using existing antd components. Of course, there may be a small number of new components that have not yet been developed. The original intention of opening the Exploration channel is to improve Ant Design together with users. If you are using this content, your feedback can help us optimize and iterate faster, and promote components to enter the development state as soon as possible. [Feedback](https://www.yuque.com/antdesign/topics) | [Alibaba Internal Feedback](https://yuque.antfin-inc.com/ui-assets/topics) --- Title: Navigation URL: https://ant.design/docs/spec/research-navigation --- Navigation is used to display where the user is in the current product and where they can go. ## Design Goals Make users clearly aware of their current position in the product and conveniently and quickly take them to where they want to go. --- ## Design Principles

Findability

Users can locate the information they want.

Efficiency

1. Multiple entry points: Provide multiple links to the same destination;

2. Shortcuts: Provide shortcuts to access content, such as related links;

3. Escape hatch: Click the logo to return to the homepage and restart the information search.

--- ## Design Suggestions ### Information Architecture • Keep the information architecture hierarchy shallow, flat, and wide as much as possible during design; • Consider navigation from the user's usage path rather than just based on the hierarchical structure; • Common organizational methods include: 1. By topic, such as the services or content categories provided by the product, which directly presents the site's content scope; 2. By audience, such as administrators, operators, users; 3. By task, such as understanding cooperation models, contacting cooperation specialists, signing process, cooperation coordination, business operation, customer service. ### Navigation Paths A complete navigation should allow users to move along multiple paths:
**A - Lateral Move**: Jump to the same level **B - Drill Down**: Enter lower-level content **C - Return**: Browse back through history or higher-level content **D - Associative Navigation**: Navigate to content based on relevance --- ## Types Correct understanding and use of navigation components are crucial to the overall product experience. We divide navigation into the following 5 types: 1. Global Navigation 2. Back Navigation 3. In-Page Navigation 4. Drill Down Navigation 5. Associative Navigation ### Global Navigation Global navigation reflects the core organizational structure of the website.
#### Sidebar Navigation - Used when there are many menus, recommended for more than 6 menu items; - Can carry multiple levels, but 1-3 levels are recommended; - Enterprise products are recommended to use sidebar navigation, which has better visibility and is easier to scan. The importance of each menu is less affected by the menu order. #### Top Navigation - The weight of each menu is often positively correlated with the order, meaning the order affects the frequency of user use; - Recommended for 2~7 content items; - Recommended for 1-2 levels; when more than 2 levels, pop-up navigation is recommended. #### Pop-Up Navigation Correct Example Incorrect Example Used to expand the navigation bearing level, suitable for large websites. Sitemap-style navigation allows users to see the available functions of the entire site at a glance. 1. Do not make users follow a narrow hover path to get navigation menus; 2. Do not make users open each layer of the menu step by step to find, inefficient and difficult; > This suggestion is only for navigation menus, not for operational menus. #### Utility Navigation Usually placed in the upper right corner of the website, it is a habitual usage. Users are used to finding these contents in this position. Content usually includes: • Global search • Notification center • Site help • Customer service information, shopping cart • Favorites • Login tools • Language switch Incorrect Example **Do not place in-page operations in utility tools.** ### Subsite Navigation Enterprise products often adopt a mixed structure of hierarchy + database in information architecture. This structure usually has deep layers. To achieve a shallow, flat, and wide perception level for users, organize several deep layers into a subsite to reduce the number of levels in a single site and reduce user cognitive load. Another subsite scenario is to face complex tasks that require a large workspace and handle tasks immersively as a subsite. The most common is the editor. In subsite mode, there is a low demand for full-site navigation functions, usually only needing to provide an exit to return to the upper level or homepage. > Here, the database is a form of information architecture where the content of each page is independent but follows a consistent format. #### Immersive Navigation Used to handle complex tasks or those requiring a large workspace. #### Multilevel Site Navigation - Used for subsites with many menus; - Subsite design should be significantly different from full-site navigation, requiring a significant transition to indicate entering a new space. ### In-Page Navigation For content navigation at lower levels of the information architecture, use in-page navigation. If the page needs to be shared with others, add a location mark in the URL. #### Page Header The page header is located above the page content, mainly for declaring the page theme, in-page information navigation, and page-level content operations. #### Tree Control Displays a multi-level structure within the page. #### Anchor Jumps between various page sections, used when the content displayed in a flat layout is too long. #### Back to Top Quickly returns to the top of the page. #### Carousel Cycles through a series of content. ### Drill Down Navigation Click to enter the lower-level content of the information architecture. Defaults to in-site navigation; opens a new tab for external sites. A typical scenario is drilling down from a list to details. ### Back Navigation #### Breadcrumbs Reflects the current page's position within the website structure. When there are fewer than three levels, there is no need to display breadcrumbs, as the global navigation can directly present the location. Users can return to the previous page through breadcrumbs. #### Back Button **Titles typically appear alongside breadcrumbs. When breadcrumbs are present, back buttons in titles are not recommended.** The back button in the page header is equivalent to a short breadcrumb, used to return to the previous level. It is suitable for subsite scenarios where full-site navigation is hidden, and users need to return to the upper level through the back button. ### Associative Navigation #### Step Bar Guides users step by step according to a predefined sequence. Displays the step bar on each page of a series of pages, marking the current page's position on this linear path. Suitable for: • Linear user visit paths; • Step bars break down complex tasks into easy-to-handle small tasks, reducing user errors and completing tasks faster. #### Previous/Next Helps us move to other closely related web pages. --- ## How to Validate Design Results To test the quality of the navigation system, conduct a stress test: parachute into the site, testing the navigation system's limits. 1. Ignore the homepage and go directly to a random page on the site; 2. Check if users can know their current position and its relation to other parts of the site. Which part of the site is this? What is the upper-level page? 3. Do they know where this page will take them? Does the link text explain the destination? --- ## Further Reading ### External Reference Articles - [Alibaba Cloud - Console Navigation System](https://xconsole.aliyun-inc.com/spec/hxzewz) - [Material Design Navigation](https://material.io/design/navigation/understanding-navigation.html#) - [Predix Navigation](https://www.predix-ui.com/#/design/foundation/navigation) - [Windows - UWP Navigation Design Basics](https://docs.microsoft.com/zh-cn/windows/uwp/design/basics/navigation-basics) - [When You Should Use a Breadcrumb Navigation?](https://uxmovement.com/navigation/when-you-should-use-a-breadcrumb-navigation/) - [Books: "Information Architecture for the World Wide Web" - Navigation Systems](https://www.oreilly.com/library/view/information-architecture-for/0596527349) - [Books: "Designing Web Navigation"](https://www.oreilly.com/library/view/designing-web-navigation/9780596528102/) --- Title: Message and Feedback URL: https://ant.design/docs/spec/research-message-and-feedback --- Used to provide feedback to the user on the results of their actions or to convey messages when necessary. ## Design Goals Ensure that users receive feedback or messages that match the context and urgency of their actions under different scenarios, achieving reasonable and effective communication. ## Feedback Methods When designing, consider the task the user is attempting to complete and the method of attention required. The feedback methods are listed below:
## When to Use
### Success #### Stay in Place **Modal Dialog** Notify users of important success results without interrupting their workflow. #### **Global Message** Display a brief success message without interrupting the user’s ongoing task. #### Redirect **Inline Text & Illustration** - Notify users of success at the end of a long-form process; - Provide detailed supplementary information (e.g., configuration details). #### **Global Message** Display a brief success message without interrupting the user’s ongoing task. ### Failure #### Stay in Place **Modal Dialog** Alert users to important actions outside the current workflow (e.g., safety warnings). #### **Alert** Inform users of critical errors that require immediate attention. #### **Form Validation** - User input does not meet field or form requirements; - User skipped required fields; - System detects errors in form data. #### **Notification** - Inform users of important issues or failure statuses that require immediate decisions; - Feedback on backend process failures & alerts. #### Redirect **Inline Text & Illustration** - Notify users of failure at the end of a long-form process due to third-party causes (e.g., application engine creation failure); - Provide detailed failure information. ### Background Operations **Notification** - Inform users of important issues or failure statuses that require immediate decisions; - Feedback on backend process results. #### **Notification Center** Notify users of related activity information (e.g., items that need user approval or the progress of user-submitted approvals). --- Title: List Page URL: https://ant.design/docs/spec/research-list --- A list page allows viewing and handling a large number of entries, often with navigation to detailed pages. Users can filter, compare, add, analyze entries, and drill down to complete detail pages from the list page. --- ## Design Goals Help users view, handle, and find entries more efficiently. ## Design Principles

Scannability

Use a consistent format to highlight key information that aids in object recognition. Utilize rich interactive layered information to reduce cognitive load.

Findability

Organize lists in a logically browsable order. Provide suitable search components to help users quickly find information.

## How to Design ### Basic Layout #### Single Column Layout Stack from top to bottom, with the data filtering module at the top. After filtering the data, users can browse and analyze from the general to the specific. #### Two-Column Layout Place the data filtering module in the sidebar when there are many filtering conditions and ample horizontal space. #### [Template - Query Table](https://preview.pro.ant.design/list/table-list) **When to Use** When each entry needs to expose many fields; use when users have an accurate query scope when searching for entries. #### Template - Standard List **When to Use** Provide an overview of each entry, with navigation to entry details by clicking the list. The page often provides statistical functions for users to understand the overall progress. It can be used as a simplified version of a workbench. #### [Template - Card List](https://preview.pro.ant.design/list/card-list) **When to Use** When users do not need to browse entries in a specific order, present each entry attractively. #### Template - Search List **When to Use** Primarily used for searching specific entry information, search results across many topics using keywords. Suitable for searching and filtering a large number of different types of content, meeting the needs of finding vague targets. **Involves Operations** Filter, search #### Template - Member Management **When to Use** Member management is used to display and manage the basic information and permissions of members within an object. Management operations usually include adding members, deleting members, assigning member roles and permissions, etc. **Involves Operations** Filter, delete, etc. ## Design Suggestions #### Batch Operations Page-level batch operations affect the entire page and can be placed at the bottom of the page. ## Further Reading #### External Reference Articles - [Canvas Filters](https://canvas.hubspot.com/patterns/filters) - [Canvas Search](https://canvas.hubspot.com/patterns/search) - [Fiori Analytical List Page](https://experience.sap.com/fiori-design-web/analytical-list-page/) - [QuickBook Table Design Rules](https://designsystem.quickbooks.com/component/tables/) - [Article: Data Table Design](https://medium.com/@taras.bakusevych/data-tables-design-3c705b106a64) - [Article: Designing Tables for Reusability](https://uxdesign.cc/designing-tables-for-reusability-490a3760533) - [Article: Affordances in Design](http://www.woshipm.com/pd/1479.html) --- Title: Form Page URL: https://ant.design/docs/spec/research-form --- A form page is a type of page used for information addition and entry. It ensures that users enter information according to requirements and submit it for system use or guide users in application settings. ## Design Goals Help users clearly understand the current page tasks, quickly find and locate modification targets, easily and accurately understand the meaning and effects of form items, while simplifying the filling process, ensuring that users can complete tasks accurately, easily, and quickly. ## Design Principles

Efficient

Use reasonable information organization and form components to enable users to quickly complete form page tasks.

Clear

1. Quickly locate important information and target options;
2. Titles, options, and prompts accurately convey meanings;
3. Allow users to perceive the cause and effect of different operations and respond promptly with relevant feedback.

Security

Reasonable mechanisms to ensure the consequences of operations, such as providing distributed or instant save mechanisms for complex forms; offering regret and quick fix functions like return, reset, cancel, clear, and undo for different scenario tasks.

### Do & Don’t When organizing and presenting form items on the form page, pay attention to concise expression, efficiency, and accuracy to avoid increasing the cost of user input. Incorrect Example Do not use different components or presentation forms for the same type of content in a form page, as it increases the user's comprehension cost.
Correct Example Incorrect Example The titles and prompts of form items should not use incomprehensible words or be too long, causing high comprehension costs. If uncommon words are unavoidable, use auxiliary elements like help descriptions.
Incorrect Example Avoid filling hints with redundant correct statements, e.g., an input hint for a form item called "Name" is "Please enter your name."
## How to Design Form page templates focus on the experience of submitting a single form. According to the task complexity, four layout solutions are provided: - Normal Layout - Task Decomposition and Arrangement - Specific Scenarios ### Normal Layout Lay out all the information that needs to be filled in. Suitable for forms with few content items that cannot be grouped by relevance. #### Template - Basic Form **When to Use** When a simple and quick task needs to be completed, e.g., creating with minimal information input. ### Task Decomposition and Arrangement Decompose large, complex tasks into multiple parts and group them by relevance to reduce user input burden. Although each part is handled individually, they are ultimately submitted together. Suitable for large, complex forms. Proper task segmentation can reduce user error rates. #### Template - Basic Step Form **When to Use** Organize the information users need to fill and confirm in a linear process, using step bars to inform users of the complete process and progress. Often, users are asked to confirm the information again before the final submission, and clear feedback is provided at the end of the process. Suitable for tasks with clear linear logic. #### Template - Grouped Form **When to Use** When the form page requires a lot of content to be filled in a single task, and different content can be classified and summarized. #### Template - Editable List (In Development) **When to Use** Dynamic Increase/Decrease: Recommended when the number of form items ≤3, and each input box does not require a separate title.
Editable Table: Recommended when the number of form items is between 2 and 5, so each row of content can be fully displayed.
Collapsible Panel Editing: Recommended when the number of form items is between 6 and 8.
Drawer Editing: Recommended when the number of form items is >8.
Rule Tree: Applied in rule editing scenarios. Suitable for pages that need to add one or more objects, and each object requires multiple groups of data to be added or edited. ### Specific Scenario Templates #### Template - Settings **When to Use** Personal profiles, application configuration, and other settings pages are infrequently used. Generally, users will not frequently modify them after operation. **Usage Suggestions** Choose one setting mode per page: > - Instant Effect Mode: Changes take effect immediately when users modify options; > - Submission Effect Mode: Use submission effect mode when there are interdependencies among settings items. Determine whether to group according to the number of settings items: > - Number <7, grouping is not recommended; > - Number 7~15, grouping is recommended; > - Number >15, tab grouping is recommended. #### [Template - Login](https://preview.pro.ant.design/user/login) Ant Design standard login template #### [Template - Register](https://preview.pro.ant.design/user/register) Ant Design standard registration template ## Design Suggestions ### Preparation - The core of a form page consists of form items. It is recommended to familiarize yourself with the [basic rules of forms](/components/form/) before designing; - Organize the information types involved in the user's current information entry tasks, and determine the components to be used according to the [Ant Design data entry rules](/docs/spec/data-entry/). ### Layout Methods In a single form page, reasonable layout should be made according to the amount of content to balance page display and user efficiency. Form page layout can be divided into four gradients from simple to complex, and each gradient is compatible with the previous layout method. #### Basic Layout Arrange all the information to be filled out from top to bottom in a single column within one area, guiding users to read vertically. According to [research](https://www.uxmatters.com/mt/archives/2006/07/label-placement-in-forms.php), this is the most efficient layout method for task completion. #### Weak Grouping Incorrect Example When space is limited, form items with shorter widths and relevant content can be grouped into one line, suggesting grouping. #### In-Area Grouping When there is a lot of content in one area that can be categorized, in-area grouping can be achieved by distinguishing titles. #### Card Grouping When there is a lot of content on a page (usually more than two screens) that can be categorized, card grouping can be used to carry it. Each card needs to include a large title. #### Determine Layout Method The determination of which layout method to use is similar to the [Detail Page](/docs/spec/detail-page#%E8%AE%BE%E8%AE%A1%E5%BB%BA%E8%AE%AE), and should be sorted out from the two dimensions of information complexity and relevance. Then choose the appropriate template to quickly build the page.
## Further Reading ### Which Modules or Components to Use - [Form](/components/form-cn#header) - [Steps](/components/steps-cn#header) ### External Reference - [Label Placement in Forms](https://www.uxmatters.com/mt/archives/2006/07/label-placement-in-forms.php) --- Title: Exception Page URL: https://ant.design/docs/spec/research-exception --- For displaying page error states. ## Design Goals Explain what went wrong, provide appropriate suggestions or actions to the user, and avoid confusion and disorientation. --- ## Design Principles

Friendly

Use friendly, clear language to express, avoiding confusing terms that might bewilder the user.

Provide Invitation

Guide users to the next level of interaction with reminders and hints, indicating what can be done on the next screen.

--- ## Types ### Error Page Displayed when a page encounters an error, it includes the following elements: 1. Illustration: Add a bit of fun to the heavy error, easing user frustration; 2. Error Code/Issue: Display specific HTTP error codes if available; 3. Error Description: Briefly describe the error cause, making it easier for users to report the issue; 4. Suggested Actions: Help users deal with the error or guide them back on the right path. #### Template - 404 **When to Use** When the page, item, resource, etc., the user requested is not found. #### Template - 403 **When to Use** No permission, which might include no application or data permissions, depending on the situation. #### Template - 500 **When to Use** When the server encounters an error and cannot provide service to the user. #### Template - Browser Incompatibility **When to Use** When the browser is incompatible, preventing users from opening the webpage.
**Design Recommendations** When the browser is incompatible, affecting the operation to different extents, use global prompts if it does not seriously impact usage, allowing users to continue. ### Empty State Displayed when there is no content/data to show to the user. An empty state is also a specific type of error page. For detailed content, please refer to the [Empty State](/docs/spec/research-empty) document. ### Load Failure **When to Use** Displayed when a page fails to load content due to various reasons such as network issues, generally combined with retry options. ### Design Recommendations The overall interaction flow of a page may consist of different states. Designers should not only focus on the ideal state but also consider various unexpected scenarios comprehensively, preventing interruptions in the user experience. - Ideal State: The state where all page modules are displayed normally; - Partial State: Some modules are missing or some content is in an empty state, refer to the design of [Empty State](/docs/spec/research-empty); - Loading State: Use Spin or Skeleton to indicate the loading state; - Error State: System errors, no permissions, etc.; - Empty State: The state where the content is completely empty, it is recommended to use guide-like [Empty State](/docs/spec/research-empty) prompts. For new users, refer to the new user guide page. --- ## Further Reading ### Related Template Documents - [Empty State](/docs/spec/research-empty) ### External Reference - [Avoid Being Embarrassed by Your Error Messages](https://www.uxmatters.com/mt/archives/2010/08/avoid-being-embarrassed-by-your-error-messages.php) - [How to fix a bad user interface](https://www.scotthurff.com/posts/why-your-user-interface-is-awkward-youre-ignoring-the-ui-stack/#partial) --- Title: Empty Status URL: https://ant.design/docs/spec/research-empty --- ## Design Goals - The empty state should provide a prompt to help users understand the reason for the empty state, avoiding confusion and misunderstanding; - Provide recommended action tips to help users get out of the empty state. --- ## Design Principles

Clarity

Inform users of the specific reason for the empty state through clear language, illustrations, etc.

Provide Invitation

Provide help text, suggested actions, and other solutions to indicate what can be done on the next screen, guiding users to take action.

### Do & Don’t Correct Example Incorrect Example --- ## Use Cases ### New User Guidance Generally, new users expect empty states to have explanatory notes and recommended actions. Empty states are very useful in scenarios of first-time use of an application or feature, as they show the functionality and process to users and help them get started quickly. To assist new users in their first use, the empty state can be filled with feature guides, help documents, etc. #### Using Guide Variations The guide consists of three parts: state prompt, help guide, and suggested actions. During design, you can choose modules based on the business process to form the page and variations. For empty state pages within a complex process, you can also provide process guide modules to help users understand the operation process globally, and provide text buttons for quick operations related to the process. ### Completion or Clearance This empty state occurs when users voluntarily delete data from the feature. For example, customers have completed all items on their task list or read all notifications. Generally, this type of scenario does not require action guidance, just use graphical elements or prompt information to explain the empty state. ### No Data The scenario of no data in the content area is displayed with a combination of graphical elements, prompt information, and suggested actions. Whether to provide suggested actions depends on the use case. --- ## Further Reading ### External Reference Articles - [Salesforce Empty State Design Guidelines](https://www.lightningdesignsystem.com/guidelines/empty-state/#Message) - [PREDIX Empty State Design Guidelines](https://www.predix-ui.com/#/design/communication/empty-states) - [Material Design Empty State Design Guidelines](https://material.io/design/communication/empty-states.html#content) --- Title: Repetition URL: https://ant.design/docs/spec/repetition --- The same elements keep repeating in the whole interface, which not only could lower the user's learning cost effectively, but also help user recognize the relevance between these elements. --- ## Repetitive elements Example of repetitive wireframe Example of repetitive design elements Example of repetitive of formats The repetitive element may be a thick rule(line), a wireframe, color, design elements, particular format, spatial relationships, etc. --- Title: React Immediately URL: https://ant.design/docs/spec/reaction --- Invitations are powerful because they directly address discoverability and provide feedback before an interaction happens. Transitions are useful because they provide visual feedback during an interaction. But another class of feedback exists. It is the feedback that happens immediately after each interaction with the system, an immediate reaction paired with the user's action. While we can't literally extend Newton's law to the world of user interfaces, we certainly can apply this principle to the way we should interact with users. When users click on a button, they expect the button to depress. When they type in a field, they expect to see characters show up in the text box. When they make a mistake, they want the application to tell them where they goofed. While there is a possibility of too much feedback (or, more accurately, too much of the wrong feedback—a concept we will discuss in the upcoming chapters), a system with little or no feedback feels sluggish and thickheaded. > **Newton's Third Law of Motion**: For every action, there is an equal and opposite reaction, from Wikipedia. --- ## Lookup Patterns example of Certain Category example of Uncertain Category Auto Complete: As the user types input into a field, a drop-down menu of matching values is displayed. Depending on the categories of search results, it can be divided into two types, Certain Category and Uncertain Category.
example of Live Search Live Suggest: Live Suggest provides real-time search term suggestions for creating a search.
--- ## Live Suggest example of Live Preview Live Preview: A Live Preview gives the users a glimpse beforehand of how the application will interpret their input once submitted. > Note: An ounce of prevention is worth a pound of cure. Use Live Previews to prevent errors.
Progressive Disclosure: When users are faced with a series of steps, it is often best to provide hints only when they are needed, instead of cluttering the interface by displaying all the hints at once. Learn more cases on [Stay on the Page/Progressive Disclosure](/docs/spec/stay#process-flows).
example of Loading Button example of Loading Table example of Loading List example of Loading Page Progress Indicator: Progress Indicators keep a conversation going with the user when the rest of the interface is currently unavailable. Common Progress Indicators, such as Loading Button, Loading Table, Loading List and Loading Page, can be displayed respectively according to the frequency and importance of operation.
example of Click Refresh Click Refresh: Click Refresh notifies the user of fresh content and provides button or tool to refresh.
example of Periodic Refresh Periodic Refresh: Periodic Refresh brings in fresh content on a periodic basis without direct user interaction. --- Title: Proximity URL: https://ant.design/docs/spec/proximity --- When several items are in close proximity to each other, they become one visual unit rather than several separate units. Otherwise, their distance should be larger and look more like several visual units. The basic purpose of proximity is to organize. To give an apparent view of the page structure and the hierarchy of information to users. --- ## The relation of vertical spacing Example of the different vertical distance Divide the hierarchy of information through three formats:「small spacing」, 「middle spacing」and「large spacing」
Example of added element In the case that the three formats are applicable, the hierarchy of information can be separated clearly through adding or cutting down the multiple of 「basic spacing」, or adding elements. > Note: in Ant Design, y = 8 + 8 \* n, among which, n >= 0, y stands for the vertical spacing and 8 represents 「basic spacing」. --- ## Relationship of horizontal spacing Example of combination and configuration To adapt to screens of different sizes, in the horizontal direction, use grid layout to arrange the components to ensure the flexibility of the layout.
Example of checkbox In the inner of a component, the horizontal spacing of elements should differ too. --- Title: Design Patterns URL: https://ant.design/docs/spec/overview --- The use of design patterns in enterprise-level businesses can significantly increase the certainty of the R&D team, save unnecessary design and maintain system consistency, allowing designers to focus on creativity where it is most needed. Design patterns adhere to Ant Design design values and provide a general solution to recurring design issues in enterprise products. The designer can directly use the design pattern to complete the interface design, or the design pattern can be used as a starting point to derive a more business-specific solution to meet the individual design needs. At the same time, this is a dynamically updated design document, and your reading and feedback is the driving force behind our progress, [GitHub Feedback Address](https://github.com/ant-design/ant-design/issues). ## Framework Information ![Structure diagram](https://gw.alipayobjects.com/zos/rmsportal/NyWYOFQxJYElAwtUfSdv.png) The complete design pattern will include examples of templates, components (ETC), and general-purpose concepts: - **Function example:** Consists of multiple templates to inspire users how to use and build a common feature. - **Template:** A page-level example that inspires users how to build a typical page in a system, such as a detail page. - **Component** - Basic components: The most basic elements of the system, such as buttons and pagers. - Business components/modules: Block-level examples, typically consisting of multiple components. - **General concepts:** Some conventions that guarantee ETC systematization, such as typesetting, fonts, and copywriting. ## Resources We work with engineers to transform design patterns into reusable code that maximizes your productivity and communication efficiency. - [Ant Design Pro](https://pro.ant.design): Out-of-the-box solution with 20+ templates and 10+ business components. - [Official UI](/components/overview): Ant Design's React UI library is a global component library with 60+ base components. - [Axure Library](http://library.ant.design/): Axure resource packs are included with the code to make your prototype look like a visual draft, including templates, components, and more. --- Title: Navigation URL: https://ant.design/docs/spec/navigation --- Broadly speaking, anything telling users where they are, where to go and how to get there can be called navigation. When using navigation or customizing navigational structures, please pay attention to following common pitfalls: - Provide visual and contextual cues as many as possible, to prevent users from getting lost - Maintain consistency between form and behavior, or reduce the number of items in navigation, to decrease user's learning cost - Minimize page transitions (i.e. reduce the number of page transitions required by a task from several to just once or twice), to ensure that user travels only a short distance from any page to another --- ## Menu Navigation menu is an effective and user-friendly way for representing site structure to users. A proper form of navigation should be utilized, once the information architecture of your site becomes clear and stable. ### Top Navigation Top navigation menu put hyperlinks in a row and present information in a simple and straightforward way. It is suitable for landing pages and consumer facing web apps. The number of first level menu items should be between 2 and 7. Title for each menu item should contain less than 15 characters. ### Side Navigation Vertical navigation is more flexible than horizontal one, menu items are easily extensible downward, and longer labels can be allowed. With help from a scrollbar, unlimited number of menu items can be supported. It is suitable for multi-level, operation intensive and dashboard-like web apps. - More layouts with navigation: [Layout](/components/layout/). --- ## Breadcrumb Breadcrumb tell users where they are now among page hierarchy, and parent-child relationships between pages. > Notes: > > 1. When hierarchy is deep, it is recommended to hide certain pages. Depth of pages shown should at best be lower than 3, and should not exceed 5. > 2. Avoid using breadcrumb as much as you can, especially when page contains other navigation components sufficiently telling where users are. --- ## Tabs Tabs categorize content, in order to present large amount of information in a limited space. User can easily switch among tab panels without transitioning from one page to another. Categories can be determined via business logics or states, label for each category should contain less than 15 characters. ### Basic Control content of the entire page. Usually used for switching among core functionalities. ### Card Control part of page content. Bordered container naturally separate it from other parts of the page. ### Pill Switch among options in a card. Usually used along with other types of tabs, so that user can navigate to intended content via quick tab switching. ### Vertical Used for large number of tab options. It can be easily extended to contain an unlimited number of categories. --- ## Steps Steps is a navigation bar guiding users to perform a task following a predefined workflow. It gives users a rough estimate about how long the task is going take, tells them which step they are in, and showcases users' progress in an explicit way. It is always a good idea to break complex and procedural task into steps. ### Horizontal Used for more than 2 but less than 5 steps. Title for each step should contain less than 12 characters. ### Vertical Usually float at the left side of pages, in a fixed position. Multi-line description can be attached to each step. Suitable for large or dynamic number of steps, i.e. time-based steps with dynamic descriptions. --- ## Pagination Used for paginating large amount of content. Users can clearly know the total amount of content, how much they have already browsed and how much remains to be browsed. ### Basic When there is a large number of rows, page size can be made customizable by users, so that users can query and browse information more flexibly and effectively. ### Mini Commonly used in a Card or a floating layer. ### Simple Commonly used in a Card or a data table, for no more than 10 pages. --- Title: Motion URL: https://ant.design/docs/spec/motion --- > [Ant Motion](https://motion.ant.design/) is an animation library based on Ant Design's principles. It is more than just a single library, but also an entire React based solution for modern applications. The goal is to help developers to apply animations in their projects with minimal efforts. Ant Motion provides animations with all levels of granularity - from single action to combination of moves. Animations bring vividness to interfaces and reinforce user experiences. ## Values of Animations - **Smooth interactions** - Animations can make user interactions more natural. - **Bring vividness** - Animations can attract users' attention and increase users' motivation to interact by bring more vividness. - **Define hierarchies** - Animations can define elements' hierarchies and logical relationships in the most intuitive way. - **Provide feedbacks** - Animations can reinforce user experiences by providing motional feedbacks. ## Effectiveness of Animations We can determine if an animation is effective or not from the following two aspects： - **Justified** - Is this animation necessary? Does this animation help its users to digest the information? An effective animation should not be redundant. - **Performant** - Is there any frame loss or lag? An effective animation must be smooth, and must not hurt the overall performance of the product. ## Principles Different from animations usage in typical front-office applications, animations in enterprise level applications spend a great amount of efforts on reinforcing user interactions and the effectiveness of those interactions. Therefore, we derived three animation design principles from Ant Design's core design language: ```jsx | demo /** * inline: true */ import { Col, Row } from 'antd'; const text = [ { title: 'Natural', img: 'https://gw.alipayobjects.com/zos/rmsportal/LyTPSGknLUlxiVdwMWyu.gif', content: 'The animation should based on law of nature. This assures the animation is smooth by its nature and intuitive to its users.', }, { title: 'Performant', img: 'https://gw.alipayobjects.com/zos/rmsportal/SQOZVQVIossbXpzDmihu.gif', content: 'The animation should have a transition time as minimal as possible so that it serves its purpose in the most effective way.', }, { title: 'Concise', img: 'https://gw.alipayobjects.com/zos/rmsportal/OkIXkscKxywYLSrilPIf.gif', content: 'The animation should be meaningful and justified. An over fancy animation will frustrate its users, and therefore should always be avoided.', }, ]; function Principle() { const childrenToRender = text.map((item) => (

{item.title}

{item.content}

)); return (
{childrenToRender}
); } export default Principle; ``` ### Natural Intuitive animations usually are backed by law of nature. This requires the animations to be smooth so that their users can feel the animations' motion being justified. A natural animation triggers its users with positive user experiences. Take button animation as an example, designers image the button as foliage on water - when you press it and release, the leave will slightly go into the water, and then pop back up, creating ripples around itself. ### Performant Enterprise level applications require highly effective user interactions. So is their animation design - with a transition time as minimal as possible. For example, compared to appearing animations, disappearing animations should not attract too much attention from their users. They just need to be concise and clear. Therefore, disappearing animations are configured to swing out with faster velocity and no disappearing delay between each list items - they disappear all at the same time as one unit. ### Concise Avoid dramatic and complicated animations. A good animation will get the job done instead of frustrating its users. For example, when a user expands a menu, his main focus is on the menu content, not the direction change of the arrow icon on the right. Therefore, the animation doesn't need to be very complicated and distracting; it changes just enough to indicate the transition.
> For more details, please go to [Ant Motion Animation Principles](https://motion.ant.design/language/basic). --- Title: Keep it Lightweight URL: https://ant.design/docs/spec/lightweight --- Fitts's Law is an ergonomic principle that ties the size of a target and its contextual proximity to ease of use. In other words, if a tool is close at hand and large enough to target, then we can improve the user's interaction. Putting tools in context makes for lightweight interaction. > **Fitts's Law**:fittsThe time to acquire a target is a function of the distance to and size of the target. It is proportional to the distance to the target and inversely proportional to the width of the target. --- ## Always-Visible Tools example of Always-Visible Tools, from Zhihu
--- ## Hover-Reveal Tools example of Hover-Reveal Tools
--- ## Toggle-Reveal Tools example of Toggle-Reveal Tools
--- ## Visible Area ≠ Clickable Area example of hypertext hot spot
example of button hot spot --- Title: Layout URL: https://ant.design/docs/spec/layout --- Spatial layout is the starting point of systematic visual design. The difference from traditional graphic design is that the layout space of UI interface should be based on the dynamic and systematic perspective. We were inspired by the architectural ethic of the architect Le Corbusier and explored the dynamic spatial order in UI design and formed the interface layout of Ant Design based on the principle of 'beauty of order', making it possible for designers to create spatial layout that comes with rational beauty. While defining the layout system in a visual system, we propose to start from the following 5 aspects:： 1. Unified Canvas Dimension 2. Adaptation 3. Grid Unit 4. Raster 5. Common Scales ## Unified Design Board Dimension In order to minimize communication cost, it is necessary to unify the size of the design board within the organization. E.g., the unified design board width of the ant design team is 1440. ## Adaptation In the design process, the designer also needs to establish the concept of adaptation. Decision needs to made for things like whether a system needs to be adapted depends on the specific situation, and/or what are the blocks that needs dynamic layout. According to statistics, mainstream screen resolution includes 1920, 1440, and 1366. Some devices still have resolution of 1280. Ant Design's two typical adaptation type: ### 1. Left-Right Layout Commonly used in design schemes for left and right layouts, the common practice is to fix the left navigation bar and dynamically scale the right work area. ![Left-Right Layout](https://gw.alipayobjects.com/zos/rmsportal/vSqMhPolCtINKLvVVdLt.png) ### 2. Top-Bottom Layout Common used in design schemes for top and bottom layouts. The practice is to define the minimum value for the marginal areas on both sides. After the blanking area reaches the limit value, the intermediate main content area is dynamically scaled. ![Top-Bottom Layout](https://gw.alipayobjects.com/zos/rmsportal/VQEiJqtZfvvdyZSKcEsE.png) The above are just two simple adaptation ideas, the actual design of a perfect adaptation program requires the designer to have front end perspective, plane composition perspective and interactive perspective. ## Grid Unit Ant Design uses the grid system to achieve the order of the visual system. The base unit of the grid is 8, which not only matches the even number of ideas but also matches most mainstream display devices. Grid system thinking can help designers quickly achieve design decisions in the layout space while simplifying communication between designers developers. ## Raster Ant Design uses a 24-grid architecture. Taking the structure of the 1440 top-bottom layout as an example, the content area with a width of 1168 is divided into 24 grids, as shown in the following picture. We set the value of the Gutter of the grid in the page, such that when the browser expands or shrinks in a certain range, the column width of the grid will expand or shrink accordingly, but the width of Gutter is always fixed. ![Raster layout](https://gw.alipayobjects.com/zos/rmsportal/YPUZpPCzFgQHVxXCIAzq.png) For developers, the grid is a way to achieve dynamic layout, however the designer's understanding of the grid is derived from the grid in the graphic design. Differences of the perspectives are likely to cause deviations that ultimately affect the degree of visual restoration, which in turn increases communication costs. Ant Design's designers keep the following 4 things in mind in the communication with engineers: 1. Clear definition of dynamic layout area 2. Try to always use even numbers 3. Delivery of critical numbers (Gutter, Column) 4. Always use beginning column and ending column to define blocks. ## Common Scales AntFin's projects cover a large number of products of different types and even different orders of magnitude. In order to help designers of various levels to have consistency and similar rhythm in designing page layout, to unify designing language and reduce the restoration losses, Ant Design proposed the concept of UI common scales. From a large amount of practices, we have extracted a set of arrays that can be used as dimensions for UI layout decision. All the numbers are multiples of 8 and have a dynamic sense of rhythm. After verification, it can help us to achieve a faster and better design decision making of layout design. ![The two arrays](https://gw.alipayobjects.com/zos/rmsportal/ZBeDQMLMHLRfmUlUaaII.png) ![Common Usages](https://gw.alipayobjects.com/zos/rmsportal/QWsZUeuqYGQJqJxIPHOx.png) ## Inspiration, But Not Limitation The result of Ant Design in layout space is not to limit design output, but to guide designers to do it better. The two 8-fold array can be made into a myriad of possibilities by permutations and combinations, but there is a difference between "simply applying a permutation" and "really well designed". We need to consider availability in the pursuit of beauty, and we're still on our way to achieve a design system that is both reasonable and elegant. There are still plenty of things to explore for enterprise-level application interface layout. translate-layout --- Title: Provide an Invitation URL: https://ant.design/docs/spec/invitation --- A common problem with many of these rich interactions (e.g. Drag and Drop, Inline Editing, and Contextual Tools) is their lack of discoverability. Providing an invitation to the user is one of the keys to successful interactive interfaces. Invitations are the prompts and cues that lead users through an interaction. They often include just-in-time tips or visual affordances that hint at what will happen next in the interface. > **Signifiers** are signals, communication devices. These signs tell you about the possible actions; what to do, and where to do it. Signifiers are often visible, audible or tangible, from the Design of Everyday Things. > **Affordances** are the relationships (read: possible actions) between an object and an entity (most often a person). The presence of an affordance is determined by the properties of the object and of the abilities of the entity who's interacting with the object, from the Design of Everyday Things. --- ## Static Invitations By providing cues for interaction directly on the page we can statically indicate to the user the expected interface behavior. Static Invitations provide cues directly on the page.
example of Text Invitation example of Blank Slate Invitation example of Unfinished Invitation Call to Action Invitations are generally provided as static instructions on the page. But visually they can be provided in many different ways such as Text Invitation, Blank Slate Invitation and Unfinished Invitation.
example 1 of Tour Invitation Tour invitation can be a nice way to explain design changes to a web application, especially for a well-designed interface. But providing tours will not solve the real problems an interface may have during interaction. > Note that make Tour Invitations short and simple, easy to exit, and clear to restart.
--- ## Dynamic Invitations Dynamic Invitations engage users at the point of the interaction and guide them through the next step of interaction.
example 1 of Hover Invitation example 2 of Hover Invitation Hover Invitation: Provide an invitation during mouse hover.
example of Inference Invitation Inference Invitation: Use visual inferences during interaction to cue users as to what the system has inferred about their intent.
example of More Content Invitation More Content Invitation: Indicate that there is more content on the page.
--- Title: Ant Design URL: https://ant.design/docs/spec/introduce ---
Ant Financial has a large number of enterprise-level products. With complex scenarios, designers and developers often need to respond fast due to frequent changes in product demands and concurrent R & D workflow. Many similar contents exist in the process. Through abstraction, we could obtain some stable and highly reusable components and pages. On the other hand, with the trend of commercialization, more and more enterprise products begin to pursue better user experiences. Under this situation, Ant User-Experience Design Team builds a design system for enterprise products based on four design values of Natural, Certain, Meaningful, and Growing. It aims to uniform the user interface specs and reduce redundancies and excessive production costs, helping product designers to focus on better user experience. --- ## Guidelines and Resources We provide comprehensive design guidelines, best practices, resources, and tools to help designers produce high-quality product prototypes. - [Design values](/docs/spec/values) - [Design patterns](/docs/spec/overview) - [Visualization](/docs/spec/visual) - [Illustrations](/docs/spec/illustration) - [Design resources](/docs/resources) - [Sketch toolbox](http://kitchen.alipay.com/) - [Articles](/docs/spec/article) ## Front-end Implementation [React](http://facebook.github.io/react/) is used to encapsulate a library of components which embody our design language. We welcome the community to implement [our design system](/docs/spec/introduce) in other front-end frameworks of their choice. - [Ant Design of React](/docs/react/introduce)（official implementation） - [NG-ZORRO - Ant Design of Angular](http://ng.ant.design) - [NG-ZORRO-MOBILE - Ant Design Mobile of Angular](http://ng.mobile.ant.design) - [Ant Design of Vue](http://antdv.com) - [Ant Design Blazor](https://antblazor.com/) - [San UI Toolkit for Ant Design](https://ecomfe.github.io/santd) - [antizer (ClojureScript)](https://github.com/priornix/antizer) - [AtomUI (.NET/C#)](https://github.com/chinware/atomui) ## Who's using Ant Design - [Ant Financial](http://www.antgroup.com/index.htm?locale=en_US) - [Alibaba](http://www.alibaba.com/) - [Tencent](http://www.tencent.com) - [Baidu](http://www.baidu.com) - [Koubei](http://www.koubei.com/) - [Meituan](http://www.meituan.com) - [Didi](http://www.xiaojukeji.com/) - [Eleme](https://www.ele.me/) - [Other Users](https://github.com/ant-design/ant-design/issues/477) > If your company or products use Ant Design, and you'd like to be added to this growing list, click [here](https://github.com/ant-design/ant-design/issues/477) to leave us a message. ## Words From Community - Hacker News: [Show HN: Antd – A set of high-quality React components](https://news.ycombinator.com/item?id=13053137) - Alligator: [Crafting Beautiful UIs in React Using Ant Design](https://alligator.io/react/beautiful-uis-ant-design/) - [Introduction to Ant Design](https://blog.logrocket.com/introduction-to-ant-design/) - [Build a React App with Ant Design Principles](https://developer.okta.com/blog/2020/09/16/ant-design-react-app) ## How to Contribute Contributions to Ant Design on GitHub are welcomed! Whether you have questions, concerns, or suggestions for improving Ant Design - please don't hesitate to reach out to us [here](https://github.com/ant-design/ant-design/issues). --- Title: Illustrations URL: https://ant.design/docs/spec/illustration ---
General
## Background information Illustrations are a key component of a brand's recognition. It is prevalent in both digital products and offline goods. Contrasting from Copyrighted information, illustrations not only carry information through intuition but also carries emotions and resulting in higher immersion and empathy for the customer. This leads to better user experience while accomplishing business goals. Illustrations contains inherit complexity due to the apparent personal style of the artist. It is a challenge to reproduce a consistent style between a team of artists, on the other hand, there is inherit risk when relying on a single artist for all the illustrations in a project. An illustration system is particular crucial in providing consistent branding. improving productivity. Avoiding risk in this regard is of great importance.
Background
## Design Principles From the most foundational design principles to the uppermost design techniques, HiTu adopted the design inspired by ETCG. Illustrations are grouped. Usable as templates when divided and entire use flows when congregated. This supplements the design with great flexibility and customization ability.
Design principle
#### HiTu Pyramid Model We concretized the 4 abstract cornerstones that make up our design strategy; Technology, Certainty, Nature, Growth. Technology represents a strong engineering foundation, providing strong support for all digital products while opening a window of possibility. As the diagram shows, we can visualize the relationships between personality and products, between past experiences and the future. The combinations between each of them could meet the demands of many different business requirements.
Pyramid model
## Colors ### Sea Hare Swatch Sea Hare's color matching system is inspired by Ant Design's application of color palette in scenes. Differing from the UI's color scheme. The color matching system used in illustrations will be relatively more vibrant and flexible. Taking inspiration from Ant Design's basic color palette, we tweaked brightness and tolerance. The result is more efficient and easy to use. Since it originates from Any Design's color palette, it integrates seamlessly with other UI assets. ### Default Asset Colors of Sea Hare Through research, we discovered blue and white accounts for a large proportion among enterprise products. We chose Geek Blue as our primary color for its technological, exploration and focused vibes.
Sea Hare's palette combined with Adobe's ternary color picker and mosaic ball, you can easily obtain the default version of the basic color palette.
# Design Assets ### Illustrations of People Natural head-to-body ratio In view of the natural design principle, we do not recommend using Q version cartoons and overly exaggerated artistic styles. Rather, we recommend a realistic head-to-body ratio.
9 variants of common professional character design Concurrently, we integrated emotions when designing the 9 common professional roles. Fusing some characteristics of the role while radiating vastly different personalities, meeting the needs of varies business requirements.
Breakdown of each character HiTu skeletal system Reusing different postures Taking the basic character design, we break down each character and rearrange them to match the desired skeleton structure. This means various postures can be reused and extended.
### Elementary Components Elementary components designed for business settings Memory comes from difference and professionalism from uniformity. Elementary Components refers to some status in the business settings that are constantly shifting and changing. We hope to achieve uniformity while not constraining creativity. To achieve a consistent sense of rhythm, we recommend a 1024\*1024 grid while maintaining a rounded corner with sizes that are multiples of 8.
# Usage How do I utilize this wealth of assets? With HiTu's design principles as a guide, I recommend designers to construct a sense of spatial awareness along the Z-axis, dividing the illustration into 3 layers of foreground, middle ground and background. Placing the key elements in the foreground (such as people, elementary components, etc), environment and context in the middle and creating atmosphere in the background. The foreground should also have the highest saturation and visibility, both decreasing in level as the level decreases.
--- Title: Icons URL: https://ant.design/docs/spec/icon --- An icon is a graphical representation of meaning. Icons can be used to express actions, state, and even to categorize data. Ant Design's icons adhere to the following two principles and are designed for cross-platform consistency: - Graphics that are clear, intuitive, and simple enjoy a higher degree of recognition and are more easily understood - All icons in the user interface should be consistent in style (detail design, perspective, stroke weight, etc.) --- ## System Icons System Icons System icons are often used to represent commonly used operations, such as: save, edit, delete. Ant Design also includes icons to represent file types and state. - [View the icons](/components/icon/) ### Key Contour Lines Ant Design's grid and key contour lines Contour lines play an important role in making various icons with the same visual effect. Please make all icons in the 1024×1024 resolution (16×16 64 times). - [Illustrator tips](https://zos.alipayobjects.com/rmsportal/hmNuLjCkBssupcZgYAde.png) Square contour Horizontal rectangle contour Circular contour Vertical rectangle contour ### Stroke Weight Correct example Incorrect example Consistent stroke weight is the key to maintaining the visual unity of the entire icon system. Ant Design's icons have a consistent line width of 72px. ### Corners Correct example Incorrect example Consistent rounding of corners and sizing of angles is also an important element in maintaining visual unity. Icons that follow Ant Design should have rounded corners and edges using a 72px radius. ### Visual Correction Correct example Incorrect example In certain special cases (for example, when the icon is too compact), adjustments to line width, outlines, or other subtle changes may be made to increase readability. ### Perspective Correct example Incorrect example Always keep a simple, flat style. Icons should not have a sense of depth nor a large amount of detail. ### Naming Conventions Naming Conventions Uniform naming conventions make finding icons faster and easier. For example, icons with a surrounding outline have a uniform "-o" suffix. ### Icon Sizing Icon Sizing Icons should be scaled according to the text size, according to the Ant Design specification. For example, icons inline with 12pt font should be 12px in size with 8px of spacing. ### Color Color The color of the icon should be consistent the color of the surrounding copy, unless the icon is being used to express state (in which case it should be colored accordingly). --- ## Business Icons Business Icons Business icons, unlike system icons, do not themselves have functional operations, but rather an abstraction that assists with copywriting. Compared to the system icon, the business icon is more rich in the details of the design, the size of the use of relatively large. > Note: Business icons design principles and system icons are basically the same, the details of the processing (such as stroke weight, fillet size, etc.) depending on the specific scene may be. ### Icon Sizing Icon Sizing In normal use, there are 32px (minimum size), 48px and 64px (maximum size) three options. ### Color Color There are two kinds of business icon, single-color (neutral color) and double-color (neutral color + primary color), the area of primary color does not exceed 40% of the entire icon. --- Title: Font URL: https://ant.design/docs/spec/font --- The font system is one of the most foundational parts of any interface design. Text is a major channel for users to understand application content and complete their work, and a well designed font system will greatly enhance the user's reading experience and work efficiency. The Ant Design typography system is based on the design principle of "dynamic order" combined with the law of natural logarithm and temperament. We strongly recommend it since it has been verified by a large number of Ant products. While defining the font system for a visual system, we propose to start from the following five aspects: 1. Font Family 2. Base Font Size 3. Font Scale & Line Height 4. Font Weight 5. Font Color --- ## Font Family In order to implement a good font system, the first thing is to choose an appropriate font family. Ant Design prefers the system default font family and then also provides a set of alternative font libraries to maintain readability for screens on different platforms and browsers and to make sure it's always user friendly, stable and professional to end user. ```css @font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji'; ``` > References：https://www.smashingmagazine.com/2015/11/using-system-ui-fonts-practical-guide/ and http://markdotto.com/2018/02/07/github-system-fonts/ In addition, in many applications, numbers often need to be displayed vertically. We set the CSS property `font-variant-numeric` to `tabular-nums;` to use [tabular figures](https://www.fonts.com/content/learning/fontology/level-3/numbers/proportional-vs-tabular-figures). > References：https://stackoverflow.com/questions/32660748/how-to-use-apples-new-san-francisco-font-on-a-webpage#comment78509178_32660790 ## Base Font Size We have updated Ant Design's base font size from the original 12 to 14 to ensure the best user reading efficiency on most common monitors based on display screen reading distance (50 cm) and optimal reading angle (0.3).
## Font Scale & Line Height The font scale and line height determine the beauty of the dynamics and order of a font system. Font scale refers to a series of font with different sizes. Line height can be understood as an invisible box wrapped outside the font.
Ant Design was inspired by the pentatonic scale and natural law to define 10 different font sizes and corresponding line heights. In Ant Design's visual system, our recommended base font size is 14, and its corresponding line height is 22. The choice of the rest of the font scale can be freely defined according to the specific circumstances. It is recommended that in a design system (except for display pages), the choice of font scale should be controlled within 3 to 5 types, and the principle of restraint should be maintained. ## Font Weight The choice of font weight is also based on the principles of order, stability, and restraint. In most cases, just regular(400) and medium(500) should be enough. In the case of bold English words, semibold(600) could be used.
## Font Color Text will be difficult to read if it is too close to the background color. To achieve barrier-free design, we follow the WCAG standard, which maintains an AAA level of contrast ratio, i.e. 7:1 or more between body text, title, and background color. ## Advanced Tips The construction of the font system is the first step to achieve "the beauty of dynamic order". In practical design, we have three more advanced tips: 1. **Establish a systematic design thinking:** In the UI design of the same system, a systematic design thinking should be established first. The primary, secondary, auxiliary, title, display, and other types of fonts are planned in a unified manner. And then make any necessary fine tuning according to the specific situation. The establishment of a systematic design approach helps to increase the consistency of horizontal font landing, improve the cost-effectiveness of font uses, and avoid unnecessary style waste. 1. **Less is more:** Visual design should be achieved with as few styles as possible. Avoid meaningless use of large numbers of font scales, colors, and font weight to emphasize visual or contrast relationships. 1. **Try to make font scale dance like a note:** When you need to expand any gap, you can try to choose the different sizes of the font from the font scale table, which will create a subtle rhythm between the word scales. --- Title: Feedback URL: https://ant.design/docs/spec/feedback --- In order to help users understand what the application is currently doing, and to refer to the user's next behavior, and to understand the results of the operation, when the user need to interact with the system , use different modes to feedback information or results. When the designer uses feedback or customizes some feedback, please note: - Provide users with necessary, positive and immediate feedback at all stages; - Avoid excessive feedback, so as not to cause unnecessary disturbance to the user, you can omit the feedback prompt at the results users can see immediately and simple operation. --- ## Prompt message Any product can not be separated from user guidance and information prompts even if the user interface is doing well. The prompt information is used to tell the user what needs to be known and what action to take. ### Alert #### Alert It is a non-blocking information display. It does not interrupt the user's current operation. It usually stays at a certain position on the page (top preferentially). The static display form of the non-floating layer is always displayed and will not disappear automatically. The user can click shut down. > Note: The close button can be added or hidden according to business needs. ### Notification #### Notification The important global notification information actively pushed by the system is displayed in the upper right corner of the system. #### Badge The message prompt for the aggregate type, generally appearing in the upper right corner of the notification icon or avatar, attracts the user's eye through a striking visual form. > Note: Relatively important and user-related information prompts, use digital precision prompts; weights are not high and are not the user's special concern message prompts, use red dot to make tips. ### Help #### Popover When the target element has further description and related operations, it can be stored in the card and displayed according to the user's operation behavior. > Note: The difference between Tooltip and Popover is that Popover can carry more complex content, such as links or buttons. #### Tooltip Used to accurately describe the pointed object, such as icons, graphics, links, etc. When the mouse is moved in, the prompt is displayed, when the mouse is moved out, the prompt is disappeared. And the complex text and operations are not carried. --- ## Process feedback Feedback of the status is given to the user as much as possible during the operation, and the immediate response will give the user a sense of trust. ### Loading status progress feedback When the operation takes a while (usually more than 2 seconds) to complete, the system should immediately give a reminder, clearly inform the loading status or loading progress bar, and maintain communication with the user.
> Note: If the loading time is long, a cancel operation should be provided. ### Input feedback During the operation, different verification rules and forms can be used to allow users to find and correct errors in time. > Note: The feedback text is followed by the block to be explained (the feedback content is generally an error description) and does not disappear automatically (it disappears when the user performs the corresponding interaction). #### Popconfirm When the operation of the target element requires further confirmation by the user, a floating layer prompt is ejected near the target element to inquire the user. --- ## Result feedback Feedback of the status is given to the user as much as possible during the operation, and the immediate response will give the user a sense of trust. ### Message The feedback floating layer triggered by an operation is centered on the top and disappears automatically, which is a lightweight reminder that does not interrupt the user's operation.
Correct Sample Incorrect Sample Since the feedback floating layer has a short presentation time (default 3s), for more important failure notifications, it is recommended to use a dialog box to notify you to avoid missing information. ### Dialog feedback The feedback floating layer triggered by an operation is located at the center of the page, and the feedback content can be closed by the confirmation or cancel button. The user cannot perform any operation when the feedback layer appears, it's for important feedback. > Note: Avoid displaying unnecessary reminders except it fails. Dialog is a strong feedback mechanism that is only needed when passing on very important and actionable information. --- Title: Make it Direct URL: https://ant.design/docs/spec/direct --- As Alan Cooper states：「Where there is output, let there be input」. This is the principle of direct manipulation. eg：Instead of editing content on a separate page, do it directly in context. --- ## In-Page Editing Example of click to edit Single-Field Inline Edit If 「readability」 is more important than 「editability」, 「click to edit」 can be used.
Example of Text link/Icon Edit If the priority is given to 「readability」 and the 「editability」 of operation lines need to be highlighted at the same time, 「text link/icon edit」can be used.
Example of Multi-Field Inline Edit Multi-Field Inline Edit > Note：In「Multi-Field Inline Edit」, there are huge different between the content and required field, So it is more needed to use the [「Explain What Just Happened」](/docs/spec/transition#解释刚刚发生了什么) in 「Use Transition」to eliminate this visual effects.
--- ## Drag and Drop Example of Drag and Drop List Drag and Drop List Drag and Drop can only be limited in one dimension（upper/down or left/right）
Example of Drag and Drop picture/file Drag and Drop picture/file
--- Title: Detail Page URL: https://ant.design/docs/spec/detail-page --- Detail Pages display the complete data to users. Users can edit the information or do other operations. ## Design Goals To increase the information viewing and searching efficiency. To raise the convenience of operation. ## Design Principles

Direct

Try to display the information as flat as possible. Do not hide or fold up the content if not necessary.

Clear hierarchy

In order to decrease the information complexity on each page, put information in levels and groups, following the principle of proximity.

Concise

Reduce the use of complex structures, try to use similar layouts and modules to reduce the interference of structural differences to users, and let them focus on information itself.

## Typical Templates ### Basic Layouts Basic Detail Pages directly show all the information at the same level of hierarchy. We suggest such method of displaying data. #### [Basic Detail Templates](https://preview.pro.ant.design/profile/basic) Basic layout templates display the main information on one whole card, using non-column split lines to separate the content into groups. **When to use** To display information with less content and low complexity. #### Document Detail Templates Document Detail Templates display the detailed information of approval documents. They use cards to separate the modules with complex content. **When to use** To display approval process and detailed approval information, as well as some approval operations. **Related operations** Pass, reject, transfer, sign, suspend and withdraw. ### Complex Layouts Deal with complex details in the following way: Divide information with high complexity and weak correlation into multiple parts. And put the parts into groups according to their relativities, with tabs, steps, cards, etc. #### [Advanced Detail Templates](https://preview.pro.ant.design/profile/advanced) **When to use** When the detail page has large and complex content, it has to be split into multiple tabs to guide users to browse information. #### Publish Process Templates Divide the content into steps, letting users to browse and operate step by step. **When to use** Such templates are suitable for developing and collaborating processes. ## Design Suggestions #### How to choose template Based on information complexity and correlation model, choose related modes to present the information, and select suitable layouts to display the contents of detail pages. #### Separation Methods Conclude the closeness of each information module according to the relevance among them. Usually, the more relevant the contents are, the closer they are to each other. - Non-column split lines: to separate relevant contents; - Full-column split lines: to divide the content into multiple parts; - Cards: to display information on one topic; - Tabs: to put the information into groups according to some feature, such as version, intention, phase, etc. #### Content Components Select presentation modes of the information according to its types and complexity. Abased on the complexity from low to high, the followings are available components: ## Read more #### Related Global Rules - [Data Format](/docs/spec/data-format) - [Button](/docs/spec/buttons) #### Related Modules or Components - [Description](/components/descriptions/) - [Collapse](/components/collapse/) - [Table](/components/table/) #### Reference - [Fiori – How to Design an Object Page](https://blogs.sap.com/2017/08/06/fiori-elements-how-to-design-an-object-page/) - [SAP Fiori 2.0: The Object Page —— Part 1: It's History](https://experience.sap.com/skillup/sap-fiori-2-0-the-object-page-part-1-its-history/) - [Object Page Floorplan](https://experience.sap.com/fiori-design-web/object-page/) - [Principle of Product Display in Supermarkets](https://experience.sap.com/fiori-design-web/object-page/) --- Title: Data List URL: https://ant.design/docs/spec/data-list --- ## Design goals - Make lists easy to scan. - Quickly find objects in the list. ## List type
### Table Emphasis on browsing. The matrix layout tends to display complex data, and the data is aligned according to the matrix layout, which is convenient for browsing data horizontally and vertically, and studying the relationship between data. Tables are used especially when the user would benefit from more data exposure without having to go into the details of the object. ### List Consider both browsing and presentation. Arranged vertically, it tends to show the basic overview of the object, and the content is displayed hierarchically, which is suitable for quick scanning. Especially when the display space is limited, such as smaller pop-up windows, sidebars, drop-down panels and other containers, use lists. ### Card list Emphasis on presentation. The grid layout has no specific browsing order, and each object has a more equal display opportunity. The grid layout is more attractive on the page and is suitable for highlighting objects. ## Operation Behavior ### Search data Select the appropriate search component. **1）Identify the main search patterns of users.** - Known Items Exploration: Start the search with verbally describable known items. - Exploratory query: search for a target with a defined but broad scope. **2）The higher the search frequency, the higher the efficiency requirements.** **3）Communicate well with developers to understand system performance and select appropriate components.** #### Inquire According to the preset conditions, select multiple query conditions and submit the acquisition query at one time. #### Filter Users adjust the filters and the results adjust accordingly. ### Search Smarter search, enter keywords to query in multiple data attributes at one time, and display the results. ### Paging By default, page loading is used to reduce user waiting. The user's browsing position in the original list should be cached, and the browsed items in the list should be marked. When the user returns to the previous page, the user returns to the original browsing position. #### Pagination Recommended by default. When used, when the content of the page is less than one page, the pager will not be displayed. #### same page load This mode can be considered when users can often find the desired item at the top of the list and there is no need to locate a specific list item, such as dynamics and emails. #### view all Use when you need to jump to the page to view the complete list. ### Navigate to details
mainly
#### By default, click on the title to navigate to the details, and you can judge how to open the details from the following angles: - From the perspective of natural interaction, **Expand the list on the same page** is more natural, and it should be noted that the height of the expanded content area should not exceed one screen; - From the perspective of the amount of information in the details, if the information display exceeds one screen, it is not convenient for the user to use the unfolding method. At this time, it is better to use **Drawer Expand**; - Details need to be shared with others separately, or complex immersive tasks, **jump to independent page** is more suitable; - There may be content that the user is interested in in each item of detail, so as to facilitate switching navigation, quickly view and process different items, you can use the ** double column display. ** ### Batch operations When the user checks the item, the batch operation mode is triggered, and the list toolbar calls out the batch operation toolbar. ### New #### New button in the upper right corner Click to trigger a new form pop-up window, drawer, page, etc. After the creation is completed, the newly created content appears in the first item of the list and is briefly highlighted. #### Dashed New Button Click New, and the object editing area will appear at the button position, and the newly created object will be displayed at this position after the creation is completed. The dotted new button position is placed at the beginning or end of the list. ### delete #### Delete directly After deletion, allow user to undo. #### Second Confirmation When clicking the delete operation, a second confirmation is required. #### Security check Destructive operations require high-level security verification to confirm operations. ### List Toolbar Common features needed to integrate lists in a small space, highly recommended. ## layout List layouts are usually tiled from top to bottom, in the following order. Among them, the exclusive area provides an expansion space for solving complex data search and data statistics content that cannot be integrated in the toolbar. ## Empty state When the list has no data or no search results, an empty state should be displayed. --- Title: Data format URL: https://ant.design/docs/spec/data-format --- ## Design Goals Standardize data expression to ensure intuitive, accurate and consistent understanding of data. ## Types ### Numerical The numerical value is used to indicate the measurement size, it can be used alone or with digital symbols. | Symbol Format | How and When to Use | Example | | --- | --- | --- | | Decimal separator | Use commas to separate groups of thousands to help users read. | 123,123,220 | | Unit of measurement | Put units of measurement in lowercase. | 123,220kg | | Percentage | To present proportionality, etc. | 12.32% | | Forward slash | To express progress with fractions. | 12/30 |
Do Don't **Position**: To let users read the data intuitively and accurately, it is necessary to make it clear and concise. In a table with numerical values, "right-aligned" method is usually adopted, which not only facilitates the user to quickly read, but also allows the user to compare the longitudinal data. ### Amount **Amount Format**: The standard format is "currency symbol + number". For example, "CNY1,123.00". **Currency Symbol**: There are two types: abbreviations letters and characters. You can check symbols for different currencies from [CURRENCY SYMBOLS](https://www.iban.com/currency-codes). | Currency Symbol | How and When to Use | Example | | --- | --- | --- | | Character | Take RMB as example, its character symbol is `¥`, placed in front of the amount. | ¥123.00 | | Letter | Take RMB as example, it is recommended to use `CNY`, which is the international currency code. | CNY123.00 | Large amount: If an amount is large, "M/Mill." (abbreviation of million) and "B/Bill." (abbreviation of billion) can be used. ### Date/Time #### Absolute Time Absolute time is for users with high time accuracy requirements, it emphasizes the precise time point of information release. Through absolute time, users can retrieve information and review the past content. **Date Format:** We suggest the following formats: | Format | How and when to use | Examples | | --- | --- | --- | | Year, month, day | In China `YYYY-MM-DD` format is used by default. | 2019-12-08 | | Terms | When a special term containing a date expressed with numbers, display a `.` between the month and the day, and quotation marks should be added before and after the term. | 6.1 children's day | | Date range | Put `~` or `-` between the date or time range (space is required before and after). | 2018-12-08 ~ 2019-12-07 | **Time Format:** | Time System | How and when to use | Examples | | --- | --- | --- | | 24-hour clock | The format is `HH:MM:SS`. Omit hours or second if not apply. Use the 24-hour clock by default. | 14:08:00 | | 12-hour clock | Use the format `H:MM:SS AM/PM` (or am/pm).  | 2:08:00 PM ~ 2:08:00 AM | **Standard format**: When put a date and a time together, show a space between them, e.g. "2019-12-08 06:00:00". #### Relative Time To the users, the accuracy of time is not so important as the immediacy of the information. In the console platform, relative time is generally used for message and notification. And users tend to pay more attention to the unit of time, instead of working out the specific time point of publication. | Time | Display form | | -------------------- | ------------------------------------------- | | Less than 1 minute | just now | | Less than 1 hour | N minutes ago | | Within 24 hours | N hours ago | | Longer than 24 hours | `MM-DD HH:MM`, e.g. "12-08 08:00" | | Longer than one year | `YYYY-MM-DD HH:MM`, e.g. "2019-12-08 08:00" | ### Data Redaction Data redaction refers to representing truncated data to protect sensitive privacy information. The rules presented here are general guidelines, which can be adjusted according to business scenarios with strong data security. #### Complete Redaction Do Don't Generally used for particularly important and sensitive information such as amount and time. All the numbers need to be hidden. And the data is replaced by `***`. #### Partial Redaction Generally used for situations that require partial information for identification. In such cases, some part of the information is truncated, but the numerical digits of the numbers need to retain. The truncated data is replaced by `*`. | Data Type | How and When to Use | Example | | --- | --- | --- | | Name | Two-character name: display the first character, followed by a `*`. | 仲\* | | | Names with three characters or more: display the first character and the last character, replace the middle character(s) with `*`. | 仲\*妮
仲\*\*妮 | | Mobile number | Keep the first three and the last four digits of the mobile number. | 186\*\*\*\*1402 | | ID number | The Chinese citizenship number consists of six address codes, eight birthdate codes, three sequential codes and one check code.

Redaction rules are classified into high, medium and low levels:
**High**: Show the first and last digits, and replace the others with `*`.
**Medium**: Show the first three and the last three. Replace the others with `*`.
**Low**: Show the first six and the last four. Replace the others with `*`. | 6\*\*\*\*\*\*\*\*\*\*\*\*\*2
213\*\*\*\*\*\*\*\*\*\*\*203
212912\*\*\*\*\*\*2233 | | Address | Keep the provinces, cities and district information, followed by several `*`. | 浙江省杭州市 西湖区 \***\*\*\*\*** | | Email | Keep the host name of the mail and the first three characters, indicate the rest information with `*`. | 123\***\*\*\*\*\*\***@163.com | | Bank card number | The bank card number consists of the issuing bank identification code (ranging from 6 to 12 digits), personal account identification (ranging from 6 to 12 digits), and a check code.

Redaction rules are classified into high, medium and low levels:
**High**: Display the last four digits, and replace the others with `*`.
**Medium**: Display the first six and the last four digits, replace the others with `*`. 
**Low**: Display the first six and the last six digits, display the remaining digits with `*`. | \*\*\*\*\*\*\*\*1208
620121\*\*1208
620121\*\*\*\*111208 | ### Data Status #### Empty State Do Don't Display `--` to express no-data status. #### Loading Use Skeleton screen when loading data. ## Reference - [Currency Symbol List](https://baike.baidu.com/item/%E8%B4%A7%E5%B8%81%E4%BB%A3%E7%A0%81/7467182?fr=aladdin) - [Time Data Formats for Different Countries](https://zh.wikipedia.org/wiki/%E5%90%84%E5%9C%B0%E6%97%A5%E6%9C%9F%E5%92%8C%E6%97%B6%E9%97%B4%E8%A1%A8%E7%A4%BA%E6%B3%95) - [Digital Specification for Publications](http://www.moe.gov.cn/ewebeditor/uploadfile/2015/01/13/20150113091154536.pdf) --- Title: Data Entry URL: https://ant.design/docs/spec/data-entry --- Data Entry is an important interactive way to retrieve information of objects since users will frequently add, change or delete information. Diverse ways for text input entry and selection entry help users finish interactions more clearly and efficiently. Designers should pay attention to things as follows: - Straightforward text should be provided as "Label" for novice users and users that access occasionally, while terminology should be provided as "Label" for domain experts. When sensitive information should be provided by users, hints can be used to specify why the system need to do so. For example, when it's necessary to retrieve a user's identity (ID) or phone number. - Allow users to get information via context to help completing their input. It avoids users to have wild guesses from the empty input through approaches like "good default values", "structured formats", "hints", "input tips" etc. --- ## Text Input Entry Input is the basic and common way for data entry, which provides a text editable component for users. ### Input It uses a single line for text input with limited length. > Note: Specific styles can be applied to some text (e.g. numbers, URL). Please refer to [Input](/components/input/). ### Textarea It's a multi-line text input for single long text. ### Tips and helps Basic style Hints is usually added in Input to help remind users, which can increase efficiency for the data entry. > Note: Input usually works together with label which is to the left of input by default, while it can be on top as well when the text is too long or in English context. However, it should be consistent within the same system. ### Search Search can help users reduce the range for target and retrieve the necessary information quickly from a huge information pool. --- ## Selection entry Allow users to select from a specific range #### Radio Button Radio button allows a user to select only one value from several options. Radio options should not be too many because all the options are default visible to a user so that the user can make the selection via comparison. > Note: Radio Button must be more than two options, and normally less than five. ### Checkbox Checkbox is used to select multiple values from several options. > Note: > > 1. Checkbox often works together with submit action for state. > 2. A single checkbox can represent the switch of two states. ### Switch It's used to switch the state of a single option. The inline label of "Switch" should be displayed clearly, e.g. Disable/Enable, Disallow/Allow etc.
Correct Sample Incorrect Sample > Note: It will trigger the state change directly when a user toggle the "Switch". ### Dropdown Dropdown provides more flexibility for the number of options, allowing a user to select one or multiple values from a list of options. > Note: > > 1. Used when there are more than five options. > 2. Options is listed with logical sorting and content should be fully displayed. ### Slider Slider allows to select a suitable value by moving the anchor in a continuous or discontinuous range. It's a better choice for reflecting options of intensities or grades, e.g. volume, brightness, color saturation etc.
> Note: Operations can be more flexible and convenient using "Slider" when precise value is not required. "NumberInput" can be worked together with Slider for precise values. ### Transfer Transfer the elements between two columns in an intuitive and efficient way. ### DatePicker DatePicker provides a visual way to browse and select a date or date range for users. --- ## Upload Upload is the process of publishing information (from local or cloud storage) to a remote server via a web page or a upload tool. ### Upload by simple clicks Normally used to upload a single file which doesn't require preview. Click the button will prompt the file selection window. ### Upload by displaying thumbnails Normally used to upload images. Users can upload images and display thumbnails in the list. The upload button will disappear when the number of images is up to a threshold. ### Upload by drag-and-drop Drag files into a specific area to upload, while it supports upload by clicking as well. > Note: Specific file size and format is required for file upload, e.g.: Please select text files (support PDF, ZIP, EXL) with size no more than 5M. Progress of uploading should be displayed. --- Title: Data Display URL: https://ant.design/docs/spec/data-display --- The suitable way to display data helps users quickly locate and browse data, and work together more efficiently. There are the following points to note when designing: - Organize the order of presentations according to the importance level of the information, the frequency of operation, and the degree of association. - Pay attention to the guidance in extreme situations. For example, the data information is too long, and the initial state when content is empty. --- ## Table The table is recognized as one of the clearest and most efficient forms of presentation data. It is often used in conjunction with other interface elements such as sorting, searching, filtering, and paging, and is suitable for information collection and display, data analysis and induction, and manipulation of structured data. It's structure is simple, it's separation and induction are clear, the information is easier to compare, and the user's receiving efficiency and understanding of the information is greatly improved. > Note: > > 1. The time, status, and action bar in the table need to keep the words intact without occupying multiple lines. > 2. When table cell is empty, use `-` to indicate that there is no data. ## Collapse Collapse guides the user to obtain information in a progressive manner by folding and arranging information, so that the interface is kept clean and the space is effectively utilized. These components are used extensively in navigation and are also suitable for lengthy, irregular content management. > Note: If the collapsed content has little conjunction to each other, you can use the more space-saving "accordion" mode - "accordion" is a special collapse that allows only a single content area to be unfolded. --- ## Card A card is a container for carrying information. There is not too much limit to the types of content that can be carried. It makes a type of information centralized, enhances the sense of block and is easier to operate. Cards are usually arranged in a grid or matrix to convey the hierarchical relationship between each other. Cards are suitable for lighter and more personalized information block display. > Note: > > 1. Cards are usually arranged according to the grid, and a maximum of four lines is recommended. > 2. In the limited card space, you need to pay attention to the spacing between the information. If the information is too long, you can cut off the information. For example, "Ant Design is suitable for the middle station..." --- ## Carousel As a set of same hierarchy content parallel display mode, often used for picture or card carousel, can be triggered by the user or the system automatically rotates. It is suitable for display blocks such as the official website home page and product introduction page. > Note: > > 1. The number of carousels should not be too much to avoid user boredom, it is best to control between 3 and 5. > 2. It is recommended to provide hints on the design to allow users to maintain a clear understanding of the number and direction of the carousel. --- ## Tree "Tree" displays the hierarchical relationship of information in the form of a step-by-step outline, which is efficient and has excellent visual visibility, making the overall information framework clear at a glance. Users can view and process multiple tree-level content at the same time. Tree is applicable to any information scenarios that need to be organized through a hierarchy, such as folders, organizational structures, taxonomy, country regions, and more. --- ## Timeline Timeline is used to display time-flow information vertically, generally recording events in time by flashback, tracking what the user is doing now and what he has done in the past. Each piece of information is time-based, and the content can cover topics, types, related additional content, and so on. Suitable for including events, tasks, calendar annotations, and other related data presentations. --- Title: Dark Mode URL: https://ant.design/docs/spec/dark --- Dark mode is a theme where all UI elements are darkened. ## When to use - Dark mode is recommended when you are in a dark environment as it prevents eye strain. - Dark mode is great for highlighting important content > It works similarly to turning off the lights in a movie theater. ## Design Principles 1. **Comfort of content** Avoid using highly contrasting colors or content in dark mode. Continuous use will bring fatigue. 2. **Consistency of Information** The information content in the dark mode needs to be consistent with the light mode, and the initialization hierarchical relationship should not be broken. ## Color In the application of colors, we are based on 12 sets of basic swatches and combine longer rule processing to make colors better blend under different environmental colors. ### Color Palette ### Color Palette Generator Additionally, we also provide a set of tools for generating color palettes in dark colors. You need to select your primary color and the background color of the page. We will generate a dark mode color palette for you. --- Title: Copywriting URL: https://ant.design/docs/spec/copywriting --- In the interface, we need to resonate with users through dialogue. Accurate and clear words are easy to understand, and a suitable tone can build a sense of trust easily. Therefore, in the interface design, copywriting should be taken seriously. There are some points to note when using and writing copy: - Consider from the user's point of view - Express consistently - Place important information in prominent positions - Professional, accurate and complete - Concise, friendly and positive --- ## Language In the interface, copywriting is the basis of our communication with users. Therefore, the expression of words should be carefully deliberate and designed. With clear, accurate, and concise copywriting, the user experience can be more user-friendly. ### Articulate foothold Correct Example Wrong Example When expressing content, the focus should be on users -- what they can do with your product? Not what you and your product are doing for them. The foothold of content representation is very important. Since it is user-centred design, copywriting should be user-centred as much as possible. > Note: Use "we" to communicate with users when they are reporting questions, suggestions or complaints to the systems, such as "We will consider your complaint.". ### Concise statement Correct Example Wrong Example Omit useless words and do not repeat facts known to users. In most situations, there is no need for the interface to describe all the details. Try to provide short and accessible content. ### Use words familiar to the user Correct Example Wrong Example Use simple, direct and easy-to-understand words. Indirect, ambiguous, obscure, and overly "refined" copywriting will increase user's cognitive load. ### Express consistently Correct Example Wrong Example The operation name and the target page title should be the same. - Use consistent words that describe the same thing; - Use consistent grammar, language and word orders of the context; - Use consistent operation names and page titles. ### Place important information in a prominent position Correct Example Wrong Example Let users see the most important content at first glance. > Note: When considering security issues, private information can be adjusted to "visible after click". ### Express completely and directly Correct Example Wrong Example When we want the user to take an action, we should focus on what the user can get and how he/she feels. Telling users the purpose or importance of the action can make them more willing to perform it.
Correct Example Wrong Example Error reporting is a common feature in the UI, and it is an important part of user experience. When the user inputs  the wrong content, your error message should be consistent with the user's cognition, and expressed in an easy-to-understand way. ### Use words precisely and completely Correct Example Wrong Example Use general basic words normatively. Spell correctly, express completely. Professional terms should be accurate, according to industry standards; the expression of time must be clear.
Correct Example Wrong Example ## Tone Language defines content, while emotions and atmosphere are expressed more in tone. The same content can be expressed in different tones to different users. Take an example, to professional operators and new users, we should use different copywriting. ### Bring each other closer Correct Example Wrong Example Don't refer to the user by using "my" and "your" in the same phrase. > Note: To avoid confusing the users, don't mix first person("I", "me", or "my") and second person("you", "your") in the same sentence. ### Be friendly and respectful Correct Example Wrong Example Give users support and encouragement, not commands or pressure. If you want to keep your users, don't blame them when things go wrong. Focus on solving problems, not blaming. ### Do not be too extreme Correct Example Wrong Example Don't use too absolute expression that will make the user uncomfortable. ## Capitalization and punctuation ### Uppercase and lowercase Correct Example Wrong Example When using the full name of the product, capitalize the first letter of each word. Write the abbreviations of product names in capital, such as ESC, SLB, etc. > People are much more used to reading words in lowercase letters, those are what our brains find easiest to scan and instantly absorb. Please avoid capitalizing whole words or phrases.
Correct Example Wrong Example Use the correct case.
Recommend Not recommend Use sentence capital case in headlines, titles, labels, menu items, buttons, etc. ### Arabic numbers Correct Example Wrong Example Users perceive numbers faster. Numbers transmit information more effectively than words. ### Omit unnecessary punctuation To help users scan the text more efficiently, unnecessary periods can be omitted. No need to use punctuation when the following elements appear alone: - Label - Title - Tips under the input box - Text in tooltip component - Sentences in the table
Correct Example Wrong Example The following elements need to be punctuated when they appear separately: - Multiple sentences or paragraphs - Any sentence before a link ### Use exclamation marks with caution Correct Example Wrong Example The exclamation mark will make the tone appear too excited, and it will easily make the atmosphere too tense. > Note: When expressing greetings or congratulations to the user, use "!" is reasonable, such as" Welcome back to the community! ". --- Title: Contrast URL: https://ant.design/docs/spec/contrast --- Contrast is one of the effective ways to add visual interest to your page, and to create an organizational hierarchy among different elements that aid user in finding the information quickly. > Note: The important rule for contrast to be effective, it must be strong. Don't be wimp. --- ## The Contrast of major and minor relationship good example bad example In order to help user make a quick operation (something like the form, modal), a more important operation or an operation with higher frequency would be emphasized. > Notes: ways of emphasizing are not just to intensify the key item. It could also weaken the other items.
Example of ignoring the primary and secondary sequence When there's something needs users to make decision prudently, the system should remain neutral. It shouldn't make the decision for users or lead them to make judgement. --- ## Contrast of whole and part Example of whole and part 1 Example of whole and part 2 Taking advantage of changing the typesetting, the typeface and the size, we highlight the different levels and differentiate the ensemble and the part, which would make the page be more flexible and rhythmic. --- ## Contrast of the state relation Example of static contrast Example of dynamic contrast Taking advantage of changing colors and adding assistant shapes, we realize the comparison of state relation, which could help users differentiate various information better The forms we usually see include 「static contrast」 and 「dynamic contrast」. --- Title: Global Styles URL: https://ant.design/docs/spec/colors --- Ant Design interprets the color system into two levels: a system-level color system and a product-level color system. The system-level color system mainly defines the basic color palette, neutral color palette and data visualization color palette in the design of Ant Financial. The product-level color system is in the specific design process, based on the color of the system to further define the tone of the product in accordance with the requirements and function of the color. --- ## Color Model Ant Design's design team preferred to design with the HSB color model, which makes it easier for designers to have a clear psychological expectation of color when adjusting colors, as well as facilitate communication in teams. ## System-level Color System Ant Design system-level color system also comes from the "natural" design language. Designers abstract the natural scenes through the capture, combined with the technical gene of Ant Financial, forming a unique 12 colors. Further through a large number of observations, to capture the different colors of natural light under the law of change, with the art of drawing ideas, the 12 colors were derived. The definition of neutral color palette is balanced with readability, aesthetics and usability. ### Base Color Palettes Ant Design's base color palette totals 120 colors, including 12 primary colors and their derivative colors. These colors can basically include the need for color in background applications design. Ant Design's color palette also has the ability to further extend. After careful elaboration by designers and programmers, we have come up with a set of color generation tools that combine the natural variation of colors. When there is a need for further color design, designers simply define the primary colors according to certain rules and will get a complete range of derived colors automatically. ### Neutral Color Palette ### Data Visualization Color Palette Data visualization color palette is based on the basic color palette and neutral color palette, and based on the principle that AntV's "effective, clear, accurate and beautiful". [View Palette](https://antv.antgroup.com/en/specification/language/palette) ### Palette Generation Tool If the above palettes do not meet your needs, you can choose a main color below, and Ant Design's color generation algorithm will generate a palette for you. ### Programmatic Usage We provide JavaScript usage for developers. ```bash npm install @ant-design/colors ``` ```js import { blue } from '@ant-design/colors'; console.log(blue); // ['#E6F4FF', '#BAE0FF', '#91CAFF', '#69B1FF', '#4096FF', '#1677FF', '#0958D9', '#003EB3', '#002C8C', '#001D66'] console.log(blue.primary); // '#1677FF' ``` More APIs: [@ant-design/colors](https://www.npmjs.com/package/@ant-design/colors) --- ## Product-level Color System ### Brand Color The brand color is one of the most intuitive visual elements used that is used to embody product characteristics and communicate ideas. When selecting colors, it is important to understand how the brand color is used in the user interface. In the basic color palette to choose the main color, we recommend choosing the color plate from the shallow depth of the sixth color as the main color. Ant Design's brand color comes from blue of the base color palette, it's Hex value is `#1677ff`, application scenarios include: key action point, the operation status, important information highlighting, graphics and other scenes. ### Functional Color Functional color represents a clear message as well as status, such as success, error, failure, reminder, link and so on. Functional color selection need to comply with the user's basic understanding of color. We suggest that the functional colors should be kept as consistent as possible under a set of product systems. Do not have too much customization to interfere with the user's cognitive experience. Ant Design's functional color palette is shown on the right: ### Neutral Color Neutral color is mainly used in a large part of the text interface, in addition to the background, borders, dividing lines, and other scenes are also very common. Neutral color definition needs to consider the difference between dark background and light background, while incorporating the WCAG 2.0 standard. The neutral color of Ant Design is based on transparency, as shown on the right: --- ## Color Application In Enterprise Product Design In the design of background applications of Ant Financial, our attitude towards color is restrained. Color is used more based on information delivery, operational guidance and interactive feedback purposes. Above these principles that do not undermine operational efficiency and affect the clear communication of information, a rational choice of color is key. Of course, with illustrations and display page can be properly broken this idea. --- Title: Cases URL: https://ant.design/docs/spec/cases --- Starting in April 2015, more and more products of Ant Financial follow Ant Design specification, covering multiple business lines and more than 80 applications. Designed for enterprise-class complex UIs, used by both professional and non-professional designers, Ant Design has a low learning curve that helps you get started fast and achieve rapid results. Currently, there are many products and sites using Ant Design. If your solutions are using Ant Design, please [leave us a message](https://github.com/ant-design/ant-design/issues/477). ## Best Practices --- ### Ant Financial Technology Cloud-oriented financial services, used by financial institutions that benefit from customized business cloud computing services. It assists financial institutions to upgrade to a new financial restructuring, promotion of capacity platforms, data and technology. [Visit](https://tech.antfin.com) ![Ant Financial Technology](https://gw.alipayobjects.com/zos/rmsportal/zQMWTCnhWwYNzEURbDUn.png) ### OceanBase Cloud Platform OceanBase Cloud is a distributed relational database in a real sense, and OceanBase Cloud Platform is the OceanBase cloud-based database service that can help users quickly create and use OceanBase service. [Visit](https://en.oceanbase.com/docs/) ![OceanBase Cloud Platform](https://gw.alipayobjects.com/zos/rmsportal/OYGCAlMwSWkdaKfxIDtz.png) ### Ant Design Pro Based on Ant Design's design values, Ant Design Pro is an enterprise-class frontend/design solution that continues to build up and refine typical template/business components/ancillary design resources based on design specifications and foundation components, Further enhance the experience of "users" and "designers" in the design and development of enterprise-class product design. [Visit](https://pro.ant.design) ![Ant Design Pro](https://gw.alipayobjects.com/zos/rmsportal/KZIUjJJZTEqMOgBHQkCb.png) ### Alibaba Cloud StreamCompute Alibaba Cloud StreamCompute is a streaming analysis platform running on Alibaba Cloud platform. It provides users with tools for real-time analysis of streaming data in the cloud. [Visit](https://data.aliyun.com/product/sc) ![Alibaba Cloud StreamCompute](https://img.alicdn.com/tfs/TB1LXWknntYBeNjy1XdXXXXyVXa-2880-1800.png) --- Title: Button URL: https://ant.design/docs/spec/buttons --- ## Design Principal - Guide users to achieve the desired actions. - Prevent user to make mistakes. ## Types ### Common Button Types
buttons
#### ① Default Button Default buttons are used for non-primary actions. If not sure which button type to choose from, the default button is always a safe bet. #### ② Primary Button Emphasize on "complete" or "recommend" action. There is at most one primary button per a button group. #### ③ Text Button Low emphasis and light-weight button type, such as actions in a table. #### ④ Icon Button Icon provides a visual clue. - It could fit more buttons in a small space. - Buttons with icon only need to provide Tooltip to indicate the meaning of the button. #### ⑤ Text Button with Icon Provides supplementary meaning to the button. ### Emphasis Common button types could be used to showcase to different **emphasis**. ### Do & Don't Don't Do Don't Do Do ### Special Button Types #### Dashed Button Guide users to add content in an area. #### Danger Button Do Do Warns users that there are risks involved in the action. #### Ghost Button Used in the dark or colored background. #### Call to Action Usually appeared alone and intend to used as a command. For example, it is used in the landing page or welcome banner. It could be as wide as its parent container. It is recommended to have just 1 "Call to Action" button in 1 screen. ## Placement Place buttons in the users' reading pattern for the ease of discovery, such as the "F-Shaped Reading Pattern" and "Z-Shaped Reading Pattern". ### How to Decide Button Placement? #### Page/Card/Section presents a subject, where it could be broken into 3 areas: - Header: subject's heading, summary and navigation - Body: detailed content - Footer: supplementary information or toolbar Place buttons in different areas could have different meanings. ### When to Put Buttons in the Footer? - Body section has collapsed or hidden content, such as it could not show the entire content in one screen; - Body section has complex content. For example, it has multiple subgroups and each subgroup has its own actions. Now it is needed to separate "Complete" action from body section to avoid confusion. In short, footer's purpose is to have a separation from body. ## Ordering ### Button Ordering Recommend to start from the reading flow, collapsed content should always be on the right. **How to Decide Button Ordering** - Conversation Flow: place buttons in the order similar to a conversation between computers and users. **Ask users the needed actions or your desired actions, then present the risks involved.** - Navigation Flow: for example, if a button represents going back, should be placed on the left implying it is going to the previous step. ### Button Group Do Don't When multiple buttons form a group, align buttons in one line with spaces in between. ### Grouping Buttons When there are too many buttons on the screen, we could group relevant buttons together and use similar design for that group. If one of the buttons is primary action, we could still use emphasis. **Collapse buttons in the order of importance**
Do Don't **Flat display of all the buttons:** could separate different groups using space; or use divider to group similar buttons. ## Label Do Don't Labels should clearly indicate to users what would happen when buttons got clicked. - Should use verb (except dropdown buttons) - Should be relevant to the context and be concise. Ant Design use "OK / Cancel" as default label, but you could still use below methods to customize the label text: - Describe the action result. > Publish, Login, Register. - If primary action means negative, stress the consequences. > Are you sure to delete it? Delete / Cancel --- Title: Alignment URL: https://ant.design/docs/spec/alignment --- As is described in the Law of Continuity of Gestalt psychology, in the perceptual process, people usually tend to understand the object in the way that it is firstly perceived, to let the straight lines be straight and let the curve lines be curve. In the design of interface, aligning the elements meets users' perception, also delivers the information to users in a smoother way. > **Gestalt psychology or gestaltism (German：Gestalttheorie)**: Gestalttheorie is an important genre of psychology. It rose in the beginning of the 20 century in Germany. The central principle of gestalt psychology is that the mind forms a global whole with self-organizing tendencies.「The whole is other than the sum of the parts.」--Quote from Wikipedia --- ## Text Alignment good example bad example If the paragraphs or the length of the words are too short or too loose, then a unified visual starting point is needed. --- ## Form Alignment example of colon alignment Colon alignment(right-align) can encircle the content into a certain range. Users can infer where the chart is through the regular arranged colon so that the speed of filling in the chart can be speeded up. --- ## Numbers Alignment good example bad example To compare the numbers faster, we suggest that all numbers should keep the same digit numbers after decimal point; meanwhile all numbers should be right-aligned. --- Title: Advanced URL: https://ant.design/docs/react/v5-for-19 --- :::info{title="Compatibility Interface"} antd v5 compatibility with React 16 ~ 18 by default. For React 19, you can use the following compatibility methods to adapt. ::: ### React 19 Compatibility Issues Since React 19 adjusted the export method of `react-dom`, antd cannot directly use the `ReactDOM.render` method. Therefore, using antd will encounter the following problems: - Wave effect does not show - Static methods of `Modal`, `Notification`, `Message` not working Therefore, you need to use a compatibility configuration to make antd work properly in React 19. ### Compatibility Methods You can choose one of the following methods, and it is recommended to use the compatibility package first. #### Compatibility Package Install the compatibility package Import the compatibility package at the application entry ```tsx import '@ant-design/v5-patch-for-react-19'; ``` #### unstableSetRender Once again, please use the compatibility package first. Only for special scenarios such as umd, micro-applications, etc., use the `unstableSetRender` method. `unstableSetRender` is a low-level registration method that allows developers to modify the rendering method of ReactDOM. Write the following code at the entry of your application: ```js import { unstableSetRender } from 'antd'; import { createRoot } from 'react-dom/client'; unstableSetRender((node, container) => { container._reactRoot ||= createRoot(container); const root = container._reactRoot; root.render(node); return async () => { await new Promise((resolve) => setTimeout(resolve, 0)); root.unmount(); }; }); ``` --- Title: Basic Usage URL: https://ant.design/docs/react/use-with-vite --- [Vite](https://vitejs.dev/) is one of the best React application development tools. Let's use `antd` within it. ## Install and Initialization Before all start, you may need install [yarn](https://github.com/yarnpkg/yarn/) or [pnpm](https://pnpm.io/) or [bun](https://bun.sh/). The tool will create and initialize environment and dependencies automatically, please try config your proxy setting, or use another npm registry if any network errors happen during it. Then we go inside `antd-demo` install dependencies and start it. ```bash $ cd antd-demo $ npm install $ npm run dev ``` Open the browser at http://localhost:5173/. It renders a header saying `Vite + React` on the page. ## Import antd Below is the default directory structure. ``` ├── public │   └── vite.svg ├── src │   └── assets │ └── react.svg │   ├── App.css │   ├── App.js │   ├── index.css │   ├── main.js │   └── logo.svg ├── index.html ├── package.json └── vite.config.ts ``` Now we install `antd` from yarn or npm or pnpm or bun. Modify `src/App.js`, import Button component from `antd`. ```jsx import React from 'react'; import { Button } from 'antd'; const App = () => (
); export default App; ``` OK, you should now see a blue primary button displayed on the page. Next you can choose any components of `antd` to develop your application. Visit other workflows of `Vite` at its [User Guide](https://vitejs.dev/). We are successfully running antd components now, go build your own application! --- Title: Basic Usage URL: https://ant.design/docs/react/use-with-umi --- In real project development, besides UI libraries like Ant Design, you may also need build tools, routing solutions, CSS solutions, data flow solutions, request libraries and request solutions, i18n solutions, permission solutions, Icons solutions, etc. We have launched [Umi](https://umijs.org/), an enterprise application framework based on React, based on the scenarios of business scenarios, which we recommend you to use in your projects. Umi is a scalable enterprise front-end application framework and the underlying front-end framework of Ant Group, which has served 10,000+ applications directly or indirectly. This article will guide you through creating a simple application from scratch using Umi, Ant Design and [Ant Design Pro](https://pro.ant.design/). ## Initialization Project The recommended way to create a Umi scaffold is using [pnpm](https://pnpm.io/) to execute the following command. ```bash $ mkdir myapp && cd myapp $ pnpm create umi ``` > If you use npm, you can run `npm create umi` for the same effect; if you use yarn, run `yarn create umi`; if you use bun, which means you are a very hipster, you can run `bunx create-umi` (note that there is a `-` between create and umi). Select "Simple App" here, because we want to start from "scratch". ```bash ? Pick Umi App Template › - Use arrow-keys. Return to submit. ❯ Simple App Ant Design Pro Vue Simple App ``` Here we recommend "pnpm". pnpm is better in speed and handling ghost dependencies. ```bash ? Pick Npm Client › - Use arrow-keys. Return to submit. npm cnpm tnpm yarn ❯ pnpm ``` For those in China, we recommend choosing "taobao", otherwise choose "npm". ```bash ? Pick Npm Registry › - Use arrow-keys. Return to submit. ❯ npm taobao ``` The tool then automatically installs the dependencies and executes the initialization script for the umi. Before starting the project, let's install some more dependencies that will be used in this tutorial. ```bash $ pnpm i @umijs/plugins -D $ pnpm i antd axios @ant-design/pro-components -S ``` `@umijs/plugins` is the official plugin set of Umi, containing a large number of plugins such as valtio, react-query, styled-components, locale, access, qiankun, etc. `antd` needs no introduction. `axios` is the request library; `@ant-design/pro-components` is the component used to generate the layouts. When finished, execute the following command to start the project. ```bash $ npm run dev umi dev info - Umi v4.0.46 ╔════════════════════════════════════════════════════╗ ║ App listening at: ║ ║ > Local: http://localhost:8000 ║ ready - ║ > Network: http://*********:8000 ║ ║ ║ ║ Now you can open browser with the above addresses↑ ║ ╚════════════════════════════════════════════════════╝ ``` Follow the prompts and click the url in the command line, which will automatically open the browser. If it goes well, you will see the following screen. ![](https://img.alicdn.com/imgextra/i2/O1CN01hWo9eO1ji9BZ1YHju_!!6000000004581-2-tps-774-928.png) ## Create New Routes We're going to write an application to display a list of products. The first step is to create the routes, which can be thought of as the different pages that make up the application. Umi users don't usually need to care about the implementation behind Umi, but in case you're wondering, Umi's routes are based on react-router@6.3 (Note: not the latest 6.4, which contains loader and action functionality that is not required for Umi). We can create routes with cli. ```bash $ npx umi g page products Write: src/pages/products.tsx Write: src/pages/products.less ``` Then modify the configuration file `.umirc.ts` with the new route declaration. ```diff import { defineConfig } from "umi"; export default defineConfig({ routes: [ { path: "/", component: "index" }, { path: "/docs", component: "docs" }, + { path: "/products", component: "products" }, ], npmClient: "pnpm", }); ``` Since the boilerplate uses configured routing, as the name implies, the routes are configured line by line by people, which is tedious but more flexible, this way you need to add the routes field to the configuration, see [Umi Documentation on Routing](https://umijs.org/docs/guides/routes). In addition, Umi also supports protocol-based routing, meaning that the file system is the route, so there is no need to configure routes to take effect. Then we edit the `src/layouts/index.tsx` file and add the navigation to the `/products` path in the global layout route. ```diff
  • Docs
    • +
  • + Products +
    • ``` Open http://localhost:8000/products and if it goes well, you will see the following page. ![](https://img.alicdn.com/imgextra/i2/O1CN01aNdyVG1bEMV7WEmBv_!!6000000003433-2-tps-712-276.png) ## Implementing Product UI components As your application grows, you'll need to share UI elements across multiple pages (or use them multiple times on a single page), and in Umi you can abstract this out into components. Let's write a ProductList component so that we can display the product list in different places. Create a new `src/components/ProductList.tsx` file with the following code. ```tsx import React from 'react'; import { Button, Popconfirm, Table } from 'antd'; import type { TableProps } from 'antd'; interface DataType { id: string; name: string; } const ProductList: React.FC<{ products: DataType[]; onDelete: (id: string) => void }> = ({ onDelete, products, }) => { const columns: TableProps['columns'] = [ { title: 'Name', dataIndex: 'name', }, { title: 'Actions', render(text, record) { return ( onDelete(record.id)}> ); }, }, ]; return ; }; export default ProductList; ``` ## Preparing Mock Data Assuming we have agreed on an API interface with the backend developers, we can now use Mock data to locally mock up the data that the API should return, so that front-end and back-end development can proceed simultaneously without the front-end work being blocked because the back-end API is still being developed. Umi provides an out-of-the-box [Mock function](https://umijs.org/docs/guides/mock) that allows you to set up Mock data in a convenient and easy way. Create a new `mock/products.ts` file in the root directory with the following code. ```ts import { defineMock } from 'umi'; type Product = { id: string; name: string; }; let products: Product[] = [ { id: '1', name: 'Umi' }, { id: '2', name: 'Ant Design' }, { id: '3', name: 'Ant Design Pro' }, { id: '4', name: 'Dva' }, ]; export default defineMock({ 'GET /api/products': (_, res) => { res.send({ status: 'ok', data: products, }); }, 'DELETE /api/products/:id': (req, res) => { products = products.filter((item) => item.id !== req.params.id); res.send({ status: 'ok' }); }, }); ``` Then visit http://localhost:8000/api/products and you will see the api response. ## Complete Products Page With the UI components and Mock data done, it's time to bring them together. The request solution is needed here, and our choice here is react-query (if you want to say @tanstack/react-query, yes, they are the same library, and @tanstack/react-query is a renamed package of react-query). So before you start, you need to change the configuration to enable the [react-query plugin for Umi](https://umijs.org/docs/max/react-query) with one click. First edit `.umirc.ts`. ```diff import { defineConfig } from "umi"; export default defineConfig({ + plugins: ['@umijs/plugins/dist/react-query'], + reactQuery: {}, routes: [ { path: "/", component: "index" }, { path: "/docs", component: "docs" }, { path: "/products", component: "products" }, ], npmClient: 'pnpm', }); ``` Edit `src/pages/products.tsx` with the following code. ```tsx import React from 'react'; import axios from 'axios'; import { useMutation, useQuery, useQueryClient } from 'umi'; import styles from './products.less'; import ProductList from '@/components/ProductList'; export default function Page() { const queryClient = useQueryClient(); const productsQuery = useQuery(['products'], { queryFn() { return axios.get('/api/products').then((res) => res.data); }, }); const productsDeleteMutation = useMutation({ mutationFn(id: string) { return axios.delete(`/api/products/${id}`); }, onSettled: () => { queryClient.invalidateQueries({ queryKey: ['products'] }); }, }); if (productsQuery.isLoading) return null; return (

    Page products

    { productsDeleteMutation.mutate(id); }} />
    ); } ``` Here, we pull the data from `/api/products` with `useQuery()` and submit a DELETE request to `/api/products/${id}` in the `onDelete` event with `useMutation()` to perform the delete operation. For more details on the use of react-query, please refer to [Umi Plugin for React Query](https://umijs.org/docs/max/react-query) and [React Query Official Website](https://tanstack.com/query/). After saving, you should see the following screen. ![](https://img.alicdn.com/imgextra/i1/O1CN014Sq3Uq1IceoHSfGrR_!!6000000000914-1-tps-550-411.gif) ## ProLayout A standard backend project generally need a layout, this layout is very often highly similar, [ProLayout](https://procomponents.ant.design/components/layout/) encapsulates the common menu, breadcrumbs, page headers and other functions, provides a non-dependent framework and an out-of-the-box advanced layout component. And support `side`, `mix`, `top` three modes, but also built-in menu selection, menu generation breadcrumbs, automatically set the logic of the page title. Modify the configuration for each route to add a name field for ProLayout to do menu rendering use. ```diff import { defineConfig } from "umi"; export default defineConfig({ routes: [ - { path: "/", component: "index" }, + { path: "/", component: "index", name: "home" }, - { path: "/docs", component: "docs" }, + { path: "/docs", component: "docs", name: "docs" }, - { path: "/products", component: "products" }, + { path: "/products", component: "products", name: "products" }, ], plugins: ["@umijs/plugins/dist/react-query"], reactQuery: {}, npmClient: "pnpm", }); ``` Edit `src/layouts/index.tsx` with the following code. ```tsx import { ProLayout } from '@ant-design/pro-components'; import { Link, Outlet, useAppData, useLocation } from 'umi'; export default function Layout() { const { clientRoutes } = useAppData(); const location = useLocation(); return ( { if (menuItemProps.isUrl || menuItemProps.children) { return defaultDom; } if (menuItemProps.path && location.pathname !== menuItemProps.path) { return ( {defaultDom} ); } return defaultDom; }} > ); } ``` Here we first use umi's `useAppData` to get the global client route `clientRoutes`, which is a nested routing object, and we pass `clientRoutes[0]` to ProLayout; then we use `useLocation()` to get the location information, which is also passed to ProLayout to decide which menu should be highlighted; we also want to do a route jump when we click on the menu, so we need to customize ProLayout's menuItemRender method. You may have found `src/layouts/index.less` has no place to refer to him, in order to keep the project file tidy, you can choose to delete him. The browser will automatically refresh at this point, and if it goes well, you'll see the following screen. ![](https://img.alicdn.com/imgextra/i2/O1CN01jLPfng1WljHFhj3mc_!!6000000002829-2-tps-1670-934.png) ## Build Application After completing the development and verifying it in the development environment, it is time to deploy it to our users by executing the following command. ```bash $ npm run build info - Umi v4.0.46 ✔ Webpack Compiled successfully in 5.31s info - File sizes after gzip: 122.45 kB dist/umi.js 575 B dist/src__pages__products.async.js 312 B dist/src__pages__index.async.js 291 B dist/layouts__index.async.js 100 B dist/layouts__index.chunk.css 55 B dist/src__pages__products.chunk.css event - Build index.html ``` The build command will package all resources, including JavaScript, CSS, Web Fonts, images, Html, etc. You can find these files in the `dist/` directory. ## Next Step We have completed a simple application and you may still have many questions, such as - How to handle errors uniformly? - How to handle more routing, such as dynamic routing, nested routing, permission routing, etc.? - How to use a data flow scheme? - How to modify webpack configuration or switch to vite build mode? - etc. You can. - Visit [Umi official website](https://umijs.org/) - Learn about [Umi's Routing](https://umijs.org/docs/guides/routes) - Learn about [Umi Max](https://umijs.org/docs/max/introduce), which is more integrated than Umi - Learn about the out-of-the-box middle and backend scaffolding [Ant Design Pro](https://pro.ant.design/) - Learn about advanced layouts [ProLayout](https://procomponents.ant.design/components/layout) - Learn about advanced tables [ProTable](https://procomponents.ant.design/components/table) --- Title: Basic Usage URL: https://ant.design/docs/react/use-with-rsbuild --- [Rsbuild](https://rsbuild.dev) is a build tool driven by Rspack. This article will try to use `Rsbuild` to create a project and import antd. ## Install and Initialization Before all start, you may need install [yarn](https://github.com/yarnpkg/yarn) or [pnpm](https://pnpm.io) or [bun](https://bun.sh). During the initialization process, `create-rsbuild` provides a series of templates for us to choose, We need choose the `React` template. The tool will create and initialize environment and dependencies automatically, please try config your proxy setting or use another npm registry if any network errors happen during it. Then we go inside project and start it. ```bash $ cd demo $ npm run dev ``` Open the browser at http://localhost:3000. It renders a title saying `Rsbuild with React` on the page, which is considered successful. ## Import antd Now we install `antd` from yarn or npm or pnpm or bun. Modify `src/App.tsx`, import Button component from `antd`. ```tsx import React from 'react'; import { Button } from 'antd'; const App: React.FC = () => (
    ); export default App; ``` OK, you should now see a blue primary button displayed on the page. Next you can choose any components of `antd` to develop your application. Visit other workflows of `Rsbuild` at its [Official documentation](https://rsbuild.dev). ### Customize Theme Ref to the [Customize Theme documentation](/docs/react/customize-theme). Modify theme with ConfigProvider: ```tsx import React from 'react'; import { ConfigProvider } from 'antd'; const App: React.FC = () => ( ); export default App; ``` We are successfully running the antd components using Rsbuild now, let’s start build your own application! --- Title: Basic Usage URL: https://ant.design/docs/react/use-with-refine --- [Refine](https://github.com/refinedev/refine) is a React meta-framework designed for CRUD-heavy web applications. Its core hooks and components streamline development by offering solutions for authentication, access control, routing, networking, state management, and i18n. It supports Ant Design with an integration package that includes ready-to-use components and hooks to connect Refine to Ant Design. This article will guide you through bootstrapping a fully-functional CRUD application example using Refine and Ant Design. ## Install and Initialization Refine integrates easily with platforms like Vite, Next.js, Remix, React Native, and Electron through a simple routing interface without additional setup. In this guide, we'll use Vite and the `refine-antd` preset from the `create refine-app` CLI for a quick start to create a new Refine project with Ant Design using predefined options. Before all start, you may need install [yarn](https://github.com/yarnpkg/yarn/) or [pnpm](https://pnpm.io/). Using the `refine-antd` preset eliminates the need for extra dependencies and add example pages built with Ant Design for a quick start. After the initialization is complete, we enter the project and start. ```bash $ cd antd-demo $ npm run dev ``` Once initialization is complete, all Ant Design configurations are done automatically, allowing you to start using Ant Design components in your Refine app. Open the browser at http://localhost:5173/ and you will see example CRUD app with Ant Design components. ![Refine Ant Design example](https://refine.ams3.cdn.digitaloceanspaces.com/example-readmes/antd-list-example.png) ## Inspection the code Let take a look at Ant Design usage in the one of the example component generated by the CLI command. ```tsx import { Create, useForm } from '@refinedev/antd'; import { Form, Input } from 'antd'; export const CategoryCreate = () => { const { formProps, saveButtonProps } = useForm(); return (
    ); }; ``` While Refine's integration offers a set of components and hooks, it is not a replacement for the Ant Design package, you will be able to use all the features of Ant Design in the same way you would use it in a regular React application. Refine's integration only provides components and hooks for an easier usage of Ant Design components in combination with Refine's features and functionalities. ## How to Add Ant Design to an Existing Refine Project You can follow the [Refine Ant Design official guide](https://refine.dev/docs/ui-integrations/ant-design/introduction/) to add Ant Design to an existing Refine project. To bootstrap a Refine app with various integration options like Next.js and Remix, use `npm create refine-app@latest` and select Ant Design as the UI framework from the CLI. For more detailed tutorials and guides with Ant Design, visit the [Refine documentation](https://refine.dev/tutorial/ui-libraries/intro/ant-design/react-router/). --- Title: Basic Usage URL: https://ant.design/docs/react/use-with-next --- [Next.js](https://nextjs.org/) is currently the most popular React server-side isomorphic framework in the world. This article will try to use `antd` components in projects created by Next.js. ## Install and Initialization Before all start, you may need install [yarn](https://github.com/yarnpkg/yarn/) or [pnpm](https://pnpm.io/) or [bun](https://bun.sh/). The tool will create and initialize environment and dependencies automatically, please try config your proxy setting, or use another npm registry if any network errors happen during it. After the initialization is complete, we enter the project and start. ```bash $ cd antd-demo $ npm run dev ``` Open the browser at http://localhost:3000/. if you see the NEXT logo, it is considered a success. ## Import antd Now we install `antd` from yarn or npm or pnpm or bun. Modify `src/app/page.tsx`, import Button component from `antd`. ```tsx import React from 'react'; import { Button } from 'antd'; const Home = () => (
    ); export default Home; ``` OK, you should now see a blue primary button displayed on the page. Next you can choose any components of `antd` to develop your application. Visit other workflows of `Next.js` at its [User Guide](https://nextjs.org/). You could find that components of antd do not have styles in the first screen. Next, you need to choose different SSR style processing methods according to the mode of Next.js. ## Using App Router Updated If you are using the App Router in Next.js and using antd as your component library, to make the antd component library work better in your Next.js application and provide a better user experience, you can try using the following method to extract and inject antd's first-screen styles into HTML to avoid page flicker. 1. Install `@ant-design/nextjs-registry` 2. Use it in `app/layout.tsx` ```tsx import React from 'react'; import { AntdRegistry } from '@ant-design/nextjs-registry'; const RootLayout = ({ children }: React.PropsWithChildren) => ( {children} ); export default RootLayout; ``` :::warning Next.js App Router currently not support using sub-components via `.` like `` and ``. Importing them from path would solve this problem. ::: For more detailed information, please refer to [with-nextjs-app-router-inline-style](https://github.com/ant-design/ant-design-examples/tree/main/examples/with-nextjs-app-router-inline-style). ## Using Pages Router If you are using the Pages Router in Next.js and using antd as your component library, to make the antd component library work better in your Next.js application and provide a better user experience, you can try using the following method to extract and inject antd's first-screen styles into HTML to avoid page flicker. 1. Install `@ant-design/cssinjs` > Notes for developers > > Please note that when you install `@ant-design/cssinjs`, you must ensure that the version is consistent with the version of `@ant-design/cssinjs` in local `node_modules` of `antd`, otherwise, multiple React instances will appear, resulting in ctx being unable to be read correctly. (Tips: you can use `npm ls @ant-design/cssinjs` command to view the local version) > > image 2. Rewrite `pages/_document.tsx` ```tsx import React from 'react'; import { createCache, extractStyle, StyleProvider } from '@ant-design/cssinjs'; import Document, { Head, Html, Main, NextScript } from 'next/document'; import type { DocumentContext } from 'next/document'; const MyDocument = () => (
    ); MyDocument.getInitialProps = async (ctx: DocumentContext) => { const cache = createCache(); const originalRenderPage = ctx.renderPage; ctx.renderPage = () => originalRenderPage({ enhanceApp: (App) => (props) => ( ), }); const initialProps = await Document.getInitialProps(ctx); const style = extractStyle(cache, true); return { ...initialProps, styles: ( <> {initialProps.styles} --- Title: Migration URL: https://ant.design/docs/react/migration-v5 --- This document will help you upgrade from antd `4.x` version to antd `5.x` version. If you are using `3.x` or older version, please refer to the previous [upgrade document](https://4x.ant.design/docs/react/migration-v4) to 4.x. ## Upgrade preparation 1. Please upgrade to the latest version of 4.x first, and remove / modify related APIs according to the console warning message. ## Incompatible changes in v5 ### Design specification - Basic rounded corner adjustment, changed from `2px` to four layers of radius, which are `2px` `4px` `6px` and `8px`. For example, radius of default Button is modified from `2px` to `6px`. - Primary color adjustment, changed from `#1890ff` to `#1677ff`. - Global shadow optimization, adjusted from three layers of shadows to two layers, which are used in common components (Card .e.g) and popup components (Dropdown .e.g). - Overall reduction in wireframe usage. ### Technology adjustment - Remove less, adopt CSS-in-JS, for better support of dynamic themes. The bottom layer uses [@ant-design/cssinjs](https://github.com/ant-design/cssinjs) as a solution. - All less files are removed, and less variables are no longer exported. - CSS files are no longer included in package. Since CSS-in-JS supports importing on demand, the original `antd/dist/antd.css` has also been abandoned. If you need to reset some basic styles, please import `antd/dist/reset.css`. - If you need to reset the style of the component, but you don't want to introduce `antd/dist/reset.css` to pollute the global style, You can try using the [App](/components/app) in the outermost layer to solve the problem that native elements do not have antd specification style. - Remove css variables and dynamic theme built on top of them. - LocaleProvider has been deprecated in 4.x (use `` instead), we removed the related folder `antd/es/locale-provider` and `antd/lib/locale-provider` in 5.x. - Replace built-in Moment.js with Dayjs. For more: [Use custom date library](/docs/react/use-custom-date-library/). - `babel-plugin-import` is no longer supported. CSS-in-JS itself has the ability to import on demand, and plugin support is no longer required. Umi users can remove related configurations. ```diff // config/config.ts export default { antd: { - import: true, }, }; ``` ### Compatibility - DO NOT support IE browser anymore. #### Component API adjustment - The classname API of the component popup box is unified to `popupClassName`, and `dropdownClassName` and other similar APIs will be replaced. - AutoComplete - Cascader - Select - TreeSelect - TimePicker - DatePicker - Mentions ```diff import { Select } from 'antd'; const App: React.FC = () => (
    - + ); } export default App; ``` - `getPopupContainer`: All `getPopupContainer` are guaranteed to return a unique div. This method will be called repeatedly under React 18 concurrent mode. - Upload List structure changes. [#34528](https://github.com/ant-design/ant-design/pull/34528) - Notification - Static methods are no longer allowed to dynamically set `prefixCls` `maxCount` `top` `bottom` `getContainer` in `open`, Notification static methods will now have only one instance. If you need a different configuration, use `useNotification`. - `close` was renamed to `destroy` to be consistent with message. - Drawer `style` & `className` are migrated to Drawer panel node, the original properties are replaced by `rootClassName` and `rootStyle`. - The deprecated `message.warn` in 4.x is now completely removed, please use `message.warning` instead. #### Component refactoring and removal - Remove `locale-provider` Directory. `LocaleProvider` was removed in v4, please use `ConfigProvider` instead. - Move Comment component into `@ant-design/compatible`. - Move PageHeader component into `@ant-design/pro-components`. ```diff - import { PageHeader, Comment } from 'antd'; + import { Comment } from '@ant-design/compatible'; + import { PageHeader } from '@ant-design/pro-components'; const App: React.FC = () => ( <> ); export default App; ``` - BackTop is deprecated in `5.0.0`, and is merged into FloatButton. ```diff - import { BackTop } from 'antd'; + import { FloatButton } from 'antd'; const App: React.FC = () => (
    - +
    ); export default App; ``` ## Start upgrading Use git to save your code and install latest version: ```bash npm install --save antd@5.x ``` If you want to use v4 deprecated component like `Comment` or `PageHeader`. You can install `@ant-design/compatible` and `@ant-design/pro-components` for compatible: ```bash npm install --save @ant-design/compatible@v5-compatible-v4 npm install --save @ant-design/pro-components ``` You can manually check the code one by one against the above list for modification. In addition, we also provide a codemod cli tool [@ant-design/codemod-v5](https://github.com/ant-design/codemod-v5) To help you quickly upgrade to v5. Before running codemod cli, please submit your local code changes. ```shell # Run directly through npx npx -p @ant-design/codemod-v5 antd5-codemod src # Or run directly through pnpm pnpm --package=@ant-design/codemod-v5 dlx antd5-codemod src ``` > Note that codemod cannot cover all scenarios, and it is recommended to check for incompatible changes one by one. ### less migration If you using antd less variables, you can use compatible package to covert it into v4 less variables and use less-loader to inject them: ```js const { theme } = require('antd/lib'); const { convertLegacyToken, defaultTheme } = require('@ant-design/compatible/lib'); const { defaultAlgorithm, defaultSeed } = theme; const mapV5Token = defaultAlgorithm(defaultSeed); const v5Vars = convertLegacyToken(mapV5Token); const mapV4Token = theme.getDesignToken(defaultTheme); const v4Vars = convertLegacyToken(mapV4Token); // Webpack Config module.exports = { // ... other config loader: 'less-loader', options: { lessOptions: { modifyVars: v5Vars, // or v4Vars }, }, }; ``` And then remove antd less reference in your less file: ```diff // Your less file -- @import (reference) '~antd/es/style/themes/index'; or -- @import '~antd/es/style/some-other-less-file-ref'; ``` ### Remove babel-plugin-import Remove `babel-plugin-import` from package.json and modify `.babelrc`: ```diff "plugins": [ - ["import", { "libraryName": "antd", "libraryDirectory": "lib"}, "antd"], ] ``` Umi user can disable by config： ```diff // config/config.ts or .umirc export default { antd: { - import: true, + import: false, }, }; ``` ### Replace Day.js locale Replace moment.js locale with day.js locale: ```diff - import moment from 'moment'; + import dayjs from 'dayjs'; - import 'moment/locale/zh-cn'; + import 'dayjs/locale/zh-cn'; - moment.locale('zh-cn'); + dayjs.locale('zh-cn'); ``` 🚨 You need to pay attention to the day.js plugin system. If you find that the function originally in moment.js cannot be used in day.js, please refer to the [day.js plugin document](https://day.js.org/docs/en/plugin/plugin). If you do not want to replace with day.js, you can use `@ant-design/moment-webpack-plugin` to keep moment.js: ```bash npm install --save-dev @ant-design/moment-webpack-plugin ``` ```javascript // webpack-config.js import AntdMomentWebpackPlugin from '@ant-design/moment-webpack-plugin'; module.exports = { // ... plugins: [new AntdMomentWebpackPlugin()], }; ``` ### Switch to theme of v4 If you don't want the style to change after upgrade, we have provided a v4 theme in `@ant-design/compatible` that can restore v4 style. ````diff ```sandpack const sandpackConfig = { dependencies: { '@ant-design/compatible': 'v5-compatible-v4', }, }; import { defaultTheme, // Default theme darkTheme, // Dark theme } from '@ant-design/compatible'; import { ConfigProvider, Button, Radio, Space } from 'antd'; export default () => ( A B C D ); ```` ### Legacy browser support Ant Design v5 using `:where` css selector to reduce CSS-in-JS hash priority. You can use `@ant-design/cssinjs` `StyleProvider` to cancel this function. Please ref [Compatible adjustment](/docs/react/customize-theme#compatible-adjustment). ## Multiple versions coexist We do not recommend multiple versions coexist, it will make the application more complex (such as style override, ConfigProvider not reused, etc.). It's better to use micro-applications such as [qiankun](https://qiankun.umijs.org/) for page level development. ### Install v5 through alias ```bash $ npm install --save antd-v5@npm:antd@5 # or $ yarn add antd-v5@npm:antd@5 # or $ pnpm add antd-v5@npm:antd@5 ``` The package.json will be: ```json { "antd": "4.x", "antd-v5": "npm:antd@5" } ``` Now, antd in your project is still v4, and antd-v5 is v5. ```tsx import React from 'react'; import { Button as Button4 } from 'antd'; // v4 import { Button as Button5 } from 'antd-v5'; // v5 export default () => ( <> ); ``` Then config `prefixCls` of ConfigProvider to avoid style conflict: ```tsx import React from 'react'; import { ConfigProvider as ConfigProvider5 } from 'antd-v5'; export default () => ( ); ``` ## Encounter problems If you encounter problems during the upgrade, please go to [GitHub issues](https://new-issue.ant.design/) for feedback. We will respond and improve this document as soon as possible. --- Title: Migration URL: https://ant.design/docs/react/migrate-less-variables --- This document contains the correspondence between all the less variables related to components in version 4.x and the Component Token in version 5.x. If you are upgrading from version 4.x to version 5.x, you can quickly find the corresponding Component Token through this comparison table. :::info{title=Note} There are still some less variables that do not have a corresponding Component Token, and these variables have been deprecated in version 5.x. ::: ## How to use Component Token We could configure global token and component token for each component through the `theme` property of ConfigProvider. ```tsx import React from 'react'; import { Checkbox, ConfigProvider, Radio } from 'antd'; const App: React.FC = () => ( Radio Checkbox ); export default App; ``` ## Component Token ### Alert | Less variables | Component Token | Note | | --- | --- | --- | | `@alert-success-border-color` | `colorSuccessBorder` | Global token | | `@alert-success-bg-color` | `colorSuccessBg` | Global token | | `@alert-success-icon-color` | `colorSuccess` | Global token | | `@alert-info-border-color` | `colorInfoBorder` | Global token | | `@alert-info-bg-color` | `colorInfoBg` | Global token | | `@alert-info-icon-color` | `colorInfo` | Global token | | `@alert-warning-border-color` | `colorWarningBorder` | Global token | | `@alert-warning-bg-color` | `colorWarningBg` | Global token | | `@alert-warning-icon-color` | `colorWarning` | Global token | | `@alert-error-border-color` | `colorErrorBorder` | Global token | | `@alert-error-bg-color` | `colorErrorBg` | Global token | | `@alert-error-icon-color` | `colorError` | Global token | | `@alert-message-color` | `colorTextHeading` | Global token | | `@alert-text-color` | `colorText` | Global Token | | `@alert-close-color` | `colorIcon` | Global token | | `@alert-close-hover-color` | `colorIconHover` | Global token | | `@alert-padding-vertical` | `defaultPadding` | Control the whole padding | | `@alert-padding-horizontal` | `defaultPadding` | Control the whole padding | | `@alert-no-icon-padding-vertical` | - | Deprecated | | `@alert-with-description-no-icon-padding-vertical` | `withDescriptionPadding` | Control the whole padding | | `@alert-with-description-padding-vertical` | `withDescriptionPadding` | Control the whole padding | | `@alert-with-description-padding` | `withDescriptionPadding` | Control the whole padding | | `@alert-icon-top` | - | Deprecated | | `@alert-with-description-icon-size` | `withDescriptionIconSize` | - | ### Anchor | Less variables | Component Token | Note | | --- | --- | --- | | `@anchor-bg` | '-' | Can be modified directly by `className` or `style` | | `@anchor-border-color` | `colorSplit` | GlobalToken | | `@anchor-link-top` | `linkPaddingBlock` | - | | `@anchor-link-left` | `linkPaddingInlineStart` | - | | `@anchor-link-padding` | - | `${linkPaddingBlock}px ${linkPaddingInlineStart}px` | ### Avatar | Less variables | Component Token | Note | | --- | --- | --- | | `@avatar-size-base` | `containerSize` | - | | `@avatar-size-lg` | `containerSizeLG` | - | | `@avatar-size-sm` | `containerSizeSM` | - | | `@avatar-font-size-base` | `textFontSize` | - | | `@avatar-font-size-lg` | `textFontSizeLG` | - | | `@avatar-font-size-sm` | `textFontSizeSM` | - | | `@avatar-bg` | - | Can be directly overridden by `className` or `style` | | `@avatar-color` | `colorTextLightSolid` | Global Token | | `@avatar-border-radius` | `borderRadius` | Global Token | | `@avatar-group-overlapping` | - | Deprecated for style change | | `@avatar-group-space` | `groupSpace` | - | | `@avatar-group-border-color` | `colorBorderBg` | Global Token | ### Badge | Less variables | Component Token | Note | | --- | --- | --- | | `@zindex-badge` | `indicatorZIndex` | - | | `@badge-height` | `indicatorHeight` | - | | `@badge-height-sm` | `indicatorHeightSM` | - | | `@badge-dot-size` | `dotSize` | - | | `@badge-font-size` | `textFontSize` | - | | `@badge-font-size-sm` | `textFontSizeSM` | - | | `@badge-font-weight` | `textFontWeight` | - | | `@badge-status-size` | `statusSize` | - | | `@badge-text-color` | `colorBgContainer` | Global Token | | `@badge-color` | `colorError` | Global Token | ### BreadCrumb | Less variables | Component Token | Note | | --- | --- | --- | | `@breadcrumb-base-color` | `itemColor` | - | | `@breadcrumb-last-item-color` | `lastItemColor` | - | | `@breadcrumb-font-size` | `fontSize` | GlobalToken | | `@breadcrumb-icon-font-size` | `iconFontSize` | - | | `@breadcrumb-link-color` | `linkColor` | - | | `@breadcrumb-link-color-hover` | `linkHoverColor` | - | | `@breadcrumb-separator-color` | `separatorColor` | - | | `@breadcrumb-separator-margin` | `separatorMargin` | - | ### Button | Less variables | Component Token | Note | | --- | --- | --- | | `@btn-font-weight` | `fontWeight` | - | | `@btn-border-radius-base` | `borderRadius` | Global Token | | `@btn-border-radius-sm` | `borderRadiusSM` | Global Token | | `@btn-border-width` | `lineWidth` | Global Token | | `@btn-border-style` | `lineStyle` | Global Token | | `@btn-shadow` | `defaultShadow` | - | | `@btn-primary-shadow` | `primaryShadow` | - | | `@btn-text-shadow` | - | Deprecated for no `text-shadow` any more | | `@btn-primary-color` | `primaryColor` | - | | `@btn-primary-bg` | `colorPrimary` | Global Token | | `@btn-default-color` | `colorText` | Global Token | | `@btn-default-bg` | `colorBgContainer` | Global Token | | `@btn-default-border` | `colorBorder` | Global Token | | `@btn-danger-color` | `dangerColor` | - | | `@btn-danger-bg` | `colorError` | Global Token | | `@btn-danger-border` | `colorError` | Global Token | | `@btn-disable-color` | `colorTextDisabled` | Global Token | | `@btn-disable-bg` | `colorBgContainerDisabled` | Global Token | | `@btn-disable-border` | `borderColorDisabled` | - | | `@btn-default-ghost-color` | `defaultGhostColor` | - | | `@btn-default-ghost-bg` | `ghostBg` | - | | `@btn-default-ghost-border` | `defaultGhostBorderColor` | - | | `@btn-font-size-lg` | `fontSizeLG` | Global Token | | `@btn-font-size-sm` | `fontSizeSM` | Global Token | | `@btn-padding-horizontal-base` | `paddingInline` | - | | `@btn-padding-horizontal-lg` | `paddingInlineLG` | - | | `@btn-padding-horizontal-sm` | `paddingInlineSM` | - | | `@btn-height-base` | `controlHeight` | Global Token | | `@btn-height-lg` | `controlHeightLG` | Global Token | | `@btn-height-sm` | `controlHeightSM` | Global Token | | `@btn-line-height` | `lineHeight` | Global Token | | `@btn-circle-size` | `controlHeight` | Global Token | | `@btn-circle-size-lg` | `controlHeightLG` | Global Token | | `@btn-circle-size-sm` | `controlHeightSM` | Global Token | | `@btn-square-size` | `controlHeight` | Global Token | | `@btn-square-size-lg` | `controlHeightLG` | Global Token | | `@btn-square-size-sm` | `controlHeightSM` | Global Token | | `@btn-square-only-icon-size` | `onlyIconSize` | - | | `@btn-square-only-icon-size-sm` | `onlyIconSizeSM` | - | | `@btn-square-only-icon-size-lg` | `onlyIconSizeLG` | - | | `@btn-group-border` | `groupBorderColor` | - | | `@btn-link-hover-bg` | `linkHoverBg` | - | | `@btn-text-hover-bg` | `textHoverBg` | - | ### Calendar | Less variables | Component Token | Note | | --- | --- | --- | | `@calendar-bg` | - | Deprecated for style change | | `@calendar-input-bg` | - | Deprecated for style change | | `@calendar-border-color` | - | Deprecated for style change | | `@calendar-item-active-bg` | `itemActiveBg` | - | | `@calendar-column-active-bg` | - | Deprecated for style change | | `@calendar-full-bg` | `fullBg` | - | | `@calendar-full-panel-bg` | `fullPanelBg` | - | ### Card | Less variables | Component Token | Note | | --- | --- | --- | | `@card-head-color` | `colorTextHeading` | Global Token | | `@card-head-background` | `headerBg` | - | | `@card-head-font-size` | `headerFontSize` | - | | `@card-head-font-size-sm` | `headerFontSizeSM` | - | | `@card-head-padding` | - | Deprecated | | `@card-head-padding-sm` | - | Deprecated | | `@card-head-height` | `headerHeight` | - | | `@card-head-height-sm` | `headerHeightSM` | - | | `@card-inner-head-padding` | - | Deprecated | | `@card-padding-base` | `cardPaddingBase` | - | | `@card-padding-base-sm` | `cardPaddingBaseSm` | - | | `@card-actions-background` | `actionsBackground` | - | | `@card-actions-li-margin` | `actionsLiMargin` | - | | `@card-skeleton-bg` | - | Deprecated in favor of internal Skeleton | | `@card-background` | `colorBgContainer` | Global Token | | `@card-shadow` | - | Could be modified by `className` or `style` directly | | `@card-radius` | `borderRadiusLG` | Global Token | | `@card-head-tabs-margin-bottom` | `tabsMarginBottom` | - | | `@card-head-extra-color` | `extraColor` | - | ### Carousel | Less variables | Component Token | Note | | --- | --- | --- | | `@carousel-dot-width` | `dotWidth` | - | | `@carousel-dot-height` | `dotHeight` | - | | `@carousel-dot-active-width` | `dotActiveWidth` | - | ### Cascader | Less variables | Component Token | Note | | --- | --- | --- | | `@cascader-bg` | - | Deprecated | | `@cascader-item-selected-bg` | `optionSelectedBg` | - | | `@cascader-menu-bg` | - | Deprecated | | `@cascader-menu-border-color-split` | `colorSplit` | Global Token | | `@cascader-dropdown-vertical-padding` | `optionPadding` | - | | `@cascader-dropdown-edge-child-vertical-padding` | `menuPadding` | - | | `@cascader-dropdown-font-size` | - | Deprecated | | `@cascader-dropdown-line-height` | `lineHeight` | Global Token | ### Checkbox | Less variables | Component Token | Note | | --- | --- | --- | | `@checkbox-size` | `controlInteractiveSize` | GlobalToken | | `@checkbox-color` | `colorPrimary` | - | | `@checkbox-check-color` | `colorWhite` | - | | `@checkbox-check-bg` | `colorPrimary` | GlobalToken | | `@checkbox-border-width` | `lineWidth` | - | | `@checkbox-border-radius` | `borderRadiusSM` | - | | `@checkbox-group-item-margin-right` | - | Deprecated for style change | ### Collapse | Less variables | Component Token | Note | | --- | --- | --- | | `@collapse-header-padding` | `headerPadding` | - | | `@collapse-header-padding-extra` | - | Depreacated | | `@collapse-header-bg` | `headerBg` | - | | `@collapse-content-padding` | `contentPadding` | - | | `@collapse-content-bg` | `contentBg` | - | | `@collapse-header-arrow-left` | - | Deprecated | ### DatePicker | Less variables | Component Token | Note | | --- | --- | --- | | `@picker-bg` | `colorBgContainer` | Global Token | | `@picker-basic-cell-hover-color` | `cellHoverBg` | - | | `@picker-basic-cell-active-with-range-color` | `cellActiveWithRangeBg` | - | | `@picker-basic-cell-hover-with-range-color` | `cellHoverWithRangeBg` | - | | `@picker-basic-cell-disabled-bg` | `cellBgDisabled` | - | | `@picker-border-color` | `colorSplit` | Global Token | | `@picker-date-hover-range-border-color` | `cellRangeBorderColor` | - | | `@picker-date-hover-range-color` | `cellHoverWithRangeColor` | - | | `@picker-time-panel-column-width` | `timeColumnWidth` | - | | `@picker-time-panel-column-height` | `timeColumnHeight` | - | | `@picker-time-panel-cell-height` | `timeCellHeight` | - | | `@picker-panel-cell-height` | `cellHeight` | - | | `@picker-panel-cell-width` | `cellWidth` | - | | `@picker-text-height` | `textHeight` | - | | `@picker-panel-without-time-cell-height` | `withoutTimeCellHeight` | - | ### Descriptions | Less variables | Component Token | Note | | --- | --- | --- | | `@descriptions-bg` | `labelBg` | - | | `@descriptions-title-margin-bottom` | `titleMarginBottom` | - | | `@descriptions-default-padding` | `padding`, `paddingLG` | GlobalToken, used as `${token.padding}px ${token.paddingLG}px` | | `@descriptions-middle-padding` | `paddingSM`, `paddingLG` | GlobalToken, used as `${token.paddingSM}px ${token.paddingLG}px` | | `@descriptions-small-padding` | `paddingXS`, `padding` | GlobalToken, used as `${token.paddingXS}px ${token.padding}px` | | `@descriptions-item-padding-bottom` | `itemPaddingBottom` | - | | `@descriptions-item-trailing-colon` | - | Deprecated for style change | | `@descriptions-item-label-colon-margin-right` | `colonMarginRight` | - | | `@descriptions-item-label-colon-margin-left` | `colonMarginLeft` | - | | `@descriptions-extra-color` | `extraColor` | - | ### Divider | Less variables | Component Token | Note | | --- | --- | --- | | --- | --- | --- | | `@divider-text-padding` | `textPaddingInline` | - | | `@divider-orientation-margin` | `orientationMargin` | - | | `@divider-color` | `colorSplit` | Global Token | | `@divider-vertical-gutter` | `verticalMarginInline` | - | ### Drawer | Less variables | Component Token | Note | | --- | --- | --- | | `@drawer-bg` | `colorBgElevated` | GlobalToken | | `@drawer-header-padding` | `padding`, `paddingLG` | GlobalToken, used as `${padding}px ${paddingLG}px` | | `@drawer-title-font-size` | `fontSizeLG` | GlobalToken | | `@drawer-title-line-height` | `lineHeightLG` | GlobalToken | | `@drawer-body-padding` | `paddingLG` | GlobalToken | | `@drawer-footer-padding-vertical` | `footerPaddingBlock` | `footerPaddingBlock` is a number without units, `@drawer-footer-padding-vertical` with units | | `@drawer-footer-padding-horizontal` | `footerPaddingInline` | `footerPaddingInline` is a number without units, `@drawer-footer-padding-horizontal` with units | ### Dropdown | Less variables | Component Token | Note | | ------------------------------------ | --------------------- | ----------- | | `@dropdown-selected-color` | `colorPrimary` | GlobalToken | | `@dropdown-menu-submenu-disabled-bg` | `colorBgElevated` | GlobalToken | | `@dropdown-selected-bg` | `controlItemBgActive` | GlobalToken | ### Empty | Less variables | Component Token | Note | | --- | --- | --- | | `@empty-font-size` | `fontSize` | GlobalToken | ### Form | Less variables | Component Token | Note | | --- | --- | --- | | `@label-required-color` | `labelRequiredMarkColor` | - | | `@label-color` | `labelColor` | - | | `@form-warning-input-bg` | - | Deprecated | | `@form-item-margin-bottom` | `itemMarginBottom` | - | | `@form-item-trailing-colon` | - | Deprecated | | `@form-vertical-label-padding` | `verticalLabelPadding` | - | | `@form-vertical-label-margin` | `verticalLabelMargin` | - | | `@form-item-label-font-size` | `labelFontSize` | - | | `@form-item-label-height` | `labelHeight` | - | | `@form-item-label-colon-margin-right` | `labelColonMarginInlineEnd` | - | | `@form-item-label-colon-margin-left` | `labelColonMarginInlineStart` | - | | `@form-error-input-bg` | - | Deprecated | ### Image | Less variables | Component Token | Note | | --- | --- | --- | | `@image-size-base` | - | Deprecated for not used | | `@image-font-size-base` | - | Deprecated for not used | | `@image-bg` | `colorFillTertiary` | GlobalToken | | `@image-color` | `colorTextLightSolid` | GlobalToken | | `@image-preview-operation-size` | `previewOperationSize` | - | | `@image-preview-operation-color` | `previewOperationColor` | - | | `@image-preview-operation-disabled-color` | `previewOperationColorDisabled` | - | ### Input | Less variables | Component Token | Note | | --- | --- | --- | | `@input-height-base` | `controlHeight` | Global Token | | `@input-height-lg` | `controlHeightLG` | Global Token | | `@input-height-sm` | `controlHeightSM` | Global Token | | `@input-padding-horizontal` | `paddingInline` | - | | `@input-padding-horizontal-base` | `paddingInline` | - | | `@input-padding-horizontal-sm` | `paddingInlineSM` | - | | `@input-padding-horizontal-lg` | `paddingInlineLG` | - | | `@input-padding-vertical-base` | `paddinBlock` | - | | `@input-padding-vertical-sm` | `paddingBlockSM` | - | | `@input-padding-vertical-lg` | `paddingBlockLG` | - | | `@input-placeholder-color` | `colorTextPlaceholder` | Global Token | | `@input-color` | `colorText` | Global Token | | `@input-icon-color` | - | 已废弃 | | `@input-border-color` | `colorBorder` | Global Token | | `@input-bg` | `colorBgContainer` | Global Token | | `@input-addon-bg` | `addonBg` | - | | `@input-hover-border-color` | `hoverBorderColor` | - | | `@input-disabled-bg` | `colorBgContainerDisabled` | Global Token | | `@input-outline-offset` | `activeShadow` | Control box-shadow when active | | `@input-icon-hover-color` | `colorIconHover` | Global Token | | `@input-disabled-color` | `colorTextDisabled` | Global Token | ### InputNumber | Less variables | Component Token | Note | | --- | --- | --- | | `@input-number-hover-border-color` | `hoverBorderColor` | - | | `@input-number-handler-active-bg` | `handleActiveBg` | - | | `@input-number-handler-hover-bg` | `handleHoverColor` | Wrong usage in 4.x, which is actually text color | | `@input-number-handler-bg` | `handleBg` | - | | `@input-number-handler-border-color` | `handleBorderColor` | - | ### Layout | Less variables | Component Token | Note | | --- | --- | --- | | `@layout-body-background` | `bodyBg` | - | | `@layout-header-background` | `headerBg` | - | | `@layout-header-height` | `headerHeight` | - | | `@layout-header-padding` | `headerPadding` | - | | `@layout-header-color` | `headerColor` | - | | `@layout-footer-padding` | `footerPadding` | - | | `@layout-footer-background` | `footerBg` | - | | `@layout-sider-background` | `siderBg` | - | | `@layout-trigger-height` | `triggerHeight` | - | | `@layout-trigger-background` | `triggerBg` | - | | `@layout-trigger-color` | `triggerColor` | - | | `@layout-zero-trigger-width` | `zeroTriggerWidth` | - | | `@layout-zero-trigger-height` | `zeroTriggerHeight` | - | | `@layout-sider-background-light` | `lightSiderBg` | - | | `@layout-trigger-background-light` | `lightTriggerBg` | - | | `@layout-trigger-color-light` | `lightTriggerColor` | - | ### List | Less variables | Component Token | Note | | --- | --- | --- | | `@list-header-background` | `headerBg` | - | | `@list-footer-background` | `footerBg` | - | | `@list-empty-text-padding` | `emptyTextPadding` | - | | `@list-item-padding` | `itemPadding` | - | | `@list-item-padding-sm` | `itemPaddingSM` | - | | `@list-item-padding-lg` | `itemPaddingLG` | - | | `@list-item-meta-margin-bottom` | `metaMarginBottom` | - | | `@list-item-meta-avatar-margin-right` | `avatarMarginRight` | - | | `@list-item-meta-title-margin-bottom` | `titleMarginBottom` | - | | `@list-customize-card-bg` | - | Deprecated for style change | | `@list-item-meta-description-font-size` | `descriptionFontSize` | - | ### Mentions | Less variables | Component Token | Note | | --- | --- | --- | | `@mentions-dropdown-bg` | `colorBgElevated` | GlobalToken | | `@mentions-dropdown-menu-item-hover-bg` | - | Deprecated | ### Menu | Less variables | Component Token | Note | | --- | --- | --- | | `@menu-inline-toplevel-item-height` | `itemHeight` | Same as `@menu-item-height` | | `@menu-item-height` | `itemHeight` | - | | `@menu-item-group-height` | `groupTitleLineHeight` | - | | `@menu-collapsed-width` | `collapsedWidth` | - | | `@menu-bg` | `itemBg` | - | | `@menu-popup-bg` | `popupBg` | - | | `@menu-item-color` | `itemColor` | - | | `@menu-inline-submenu-bg` | `subMenuItemBg` | - | | `@menu-highlight-color` | `itemSelectedColor` | - | | `@menu-highlight-danger-color` | `dangerItemSelectedColor` | - | | `@menu-item-active-bg` | `itemActiveBg` | - | | `@menu-item-active-danger-bg` | `dangerItemActiveBg` | - | | `@menu-item-active-border-width` | `activeBarBorderWidth` | - | | `@menu-item-group-title-color` | `groupTitleColor` | - | | `@menu-item-vertical-margin` | `itemMarginBlock` | - | | `@menu-item-font-size` | `fontSize` | Global Token | | `@menu-item-boundary-margin` | - | Deprecated in favor of new style, use `itemMarginBlock` instead | | `@menu-item-padding-horizontal` | `itemPaddingInline` | - | | `@menu-item-padding` | - | Depreacated, use `itemPaddingInline` and `itemHeight` instead | | `@menu-horizontal-line-height` | `horizontalLineHeight` | - | | `@menu-icon-margin-right` | `iconMarginInlineEnd` | - | | `@menu-icon-size` | `iconSize` | - | | `@menu-icon-size-lg` | `horizontalLineHeight` | - | | `@menu-dark-color` | `darkItemColor` | - | | `@menu-dark-danger-color` | `darkDangerItemColor` | - | | `@menu-dark-bg` | `darkItemBg` | - | | `@menu-dark-arrow-color` | - | Deprecated, and same as text color | | `@menu-dark-inline-submenu-bg` | `darkSubMenuItemBg` | - | | `@menu-dark-highlight-color` | `darkItemSelectedColor` | - | | `@menu-dark-item-active-bg` | `darkItemSelectedBg` | - | | `@menu-dark-item-active-danger-bg` | `darkDangerItemSelectedBg` | - | | `@menu-dark-selected-item-icon-color` | - | Deprecated, same as `darkItemSelectedColor` | | `@menu-dark-selected-item-text-color` | - | Deprecated, same as `darkItemSelectedColor` | | `@menu-dark-item-hover-bg` | `darkItemHoverBg` | - | ### Message | Less variables | Component Token | Note | | --- | --- | --- | | `@zindex-message` | `zIndexPopup` | - | | `@message-notice-content-padding` | `contentPadding` | - | | `@message-notice-content-bg` | `contentBg` | - | ### Modal | Less variables | Component Token | Note | | --- | --- | --- | | `@modal-header-padding-vertical` | - | Deprecated for style change | | `@modal-header-padding-horizontal` | - | Deprecated for style change | | `@modal-body-padding` | - | Deprecated for style change | | `@modal-header-bg` | `headerBg` | - | | `@modal-header-padding` | - | Deprecated for style change | | `@modal-header-border-width` | - | Deprecated for style change | | `@modal-header-border-style` | - | Deprecated for style change | | `@modal-header-title-line-height` | `titleLineHeight` | - | | `@modal-header-title-font-size` | `titleFontSize` | - | | `@modal-header-border-color-split` | - | Deprecated for style change | | `@modal-header-close-size` | - | Deprecated for style change | | `@modal-content-bg` | `contentBg` | - | | `@modal-heading-color` | `titleColor` | - | | `@modal-close-color` | `colorIcon` | GlobalToken | | `@modal-footer-bg` | `footerBg` | - | | `@modal-footer-border-color-split` | - | Deprecated for style change | | `@modal-footer-border-style` | - | Deprecated for style change | | `@modal-footer-padding-vertical` | - | Deprecated for style change | | `@modal-footer-padding-horizontal` | - | Deprecated for style change | | `@modal-footer-border-width` | - | Deprecated for style change | | `@modal-mask-bg` | `colorBgMask` | GlobalToken | | `@modal-confirm-body-padding` | - | Deprecated for style change | | `@modal-confirm-title-font-size` | `titleFontSize` | - | | `@modal-border-radius` | `borderRadiusLG` | GlobalToken | ### Pagination | Less variables | Component Token | Note | | --- | --- | --- | | `@pagination-item-bg` | `itemBg` | - | | `@pagination-item-size` | `itemSize` | - | | `@pagination-item-size-sm` | `itemSizeSM` | - | | `@pagination-font-family` | `fontFamily` | GlobalToken | | `@pagination-font-weight-active` | `fontWeightStrong` | GlobalToken | | `@pagination-item-bg-active` | `itemActiveBg` | - | | `@pagination-item-link-bg` | `itemLinkBg` | - | | `@pagination-item-disabled-color-active` | `itemDisabledColorActive` | - | | `@pagination-item-disabled-bg-active` | `itemDisabledBgActive` | - | | `@pagination-item-input-bg` | `itemInputBg` | - | | `@pagination-mini-options-size-changer-top` | `miniOptionsSizeChangerTop` | - | ### Popover> | Less variables | Component Token | Note | | --- | --- | --- | | `@popover-bg` | `colorBgElevated` | GlobalToken | | `@popover-color` | `colorText` | GlobalToken | | `@popover-min-width` | `minWidth` | - | | `@popover-min-height` | - | Deprecated for style change | | `@popover-arrow-width` | `sizePopupArrow` | GlobalToken | | `@popover-arrow-color` | - | Deprecated for style change | | `@popover-arrow-outer-color` | - | Deprecated for style change | | `@popover-distance` | `marginXXS` | Global Token | | `@popover-padding-horizontal` | - | Deprecated for style change | ### Progress | Less variables | Component Token | Note | | --- | --- | --- | | `@progress-default-color` | `defaultColor` | - | | `@progress-remaining-color` | `remainingColor` | - | | `@progress-info-text-color` | `colorText` | Global Token | | `@progress-text-color` | `circleTextColor` | - | | `@progress-radius` | `lineBorderRadius` | - | | `@progress-steps-item-bg` | `remainingColor` | - | | `@progress-text-font-size` | `fontSizeSM` | Global Token | | `@progress-circle-text-font-size` | `circleTextFontSize` | - | ### Radio | Less variables | Component Token | Note | | --- | --- | --- | | `@radio-size` | `radioSize` | - | | `@radio-top` | - | Deprecated | | `@radio-border-width` | `lineWidth` | Global Token | | `@radio-dot-size` | `dotSize` | - | | `@radio-dot-color` | - | Deprecated | | `@radio-dot-disabled-color` | `dotColorDisabled` | - | | `@radio-solid-checked-color` | `buttonSolidCheckedColor` | - | | `@radio-button-bg` | `buttonBg` | - | | `@radio-button-checked-bg` | `buttonCheckedBg` | - | | `@radio-button-color` | `buttonColor` | - | | `@radio-button-hover-color` | `colorPrimaryHover` | Global Token | | `@radio-button-active-color` | `colorPrimaryActive` | Global Token | | `@radio-button-padding-horizontal` | `buttonPaddingInline` | - | | `@radio-disabled-button-checked-bg` | `buttonCheckedBgDisabled` | - | | `@radio-disabled-button-checked-color` | `buttonCheckedColorDisabled` | - | | `@radio-wrapper-margin-right` | `wrapperMarginInlineEnd` | - | ### Rate | Less variables | Component Token | Note | | --- | --- | --- | | `@rate-star-color` | `starColor` | - | | `@rate-star-bg` | `starBg` | - | | `@rate-star-size` | `starSize` | - | | `@rate-star-hover-scale` | `starHoverScale` | - | ### Result | Less variables | Component Token | Note | | --- | --- | --- | | `@result-icon-font-size` | `iconFontSize` | - | | `@result-title-font-size` | `titleFontSize` | - | | `@result-subtitle-font-size` | `subtitleFontSize` | - | | `@result-extra-margin` | `extraMargin` | - | ### Segment | Less variables | Component Token | Note | | --- | --- | --- | | `@segmented-container-padding` | `padding` | - | | `@segmented-label-color` | `itemColor` | - | | `@segmented-hover-bg` | `itemHoverBg` | - | | `@segmented-bg` | - | Could be customized with `className` or `style` | | `@segmented-label-hover-color` | `itemHoverColor` | - | | `@segmented-selected-bg` | `itemSelectedBg` | - | ### Select | Less variables | Component Token | Note | | --- | --- | --- | | `@select-border-color` | `colorBorder` | Global Token | | `@select-item-selected-color` | `optionSelectedColor` | - | | `@select-item-selected-font-weight` | `optionSelectedFontWeight` | - | | `@select-dropdown-bg` | `colorBgElevated` | Global Token | | `@select-item-selected-bg` | `optionSelectedBg` | - | | `@select-item-active-bg` | `optionActiveBg` | - | | `@select-dropdown-vertical-padding` | `optionPadding` | Control the whole padding | | `@select-dropdown-font-size` | `optionFontSize` | - | | `@select-dropdown-line-height` | `optionLineHeight` | - | | `@select-dropdown-height` | `optionHeight` | - | | `@select-background` | `selectorBg` | - | | `@select-clear-background` | `clearBg` | - | | `@select-selection-item-bg` | `multipleItemBg` | - | | `@select-selection-item-border-color` | `multipleItemBorderColor` | - | | `@select-single-item-height-lg` | `singleItemHeightLG` | - | | `@select-multiple-item-height` | `multipleItemHeight` | - | | `@select-multiple-item-height-lg` | `multipleItemHeightLG` | - | | `@select-multiple-item-spacing-half` | - | Deprecated | | `@select-multiple-disabled-background` | `multipleSelectorBgDisabled` | - | | `@select-multiple-item-disabled-color` | `multipleItemColorDisabled` | - | | `@select-multiple-item-disabled-border-color` | `multipleItemBorderColorDisabled` | - | ### Skeleton | Less variables | Component Token | Note | | --- | --- | --- | | `@skeleton-block-radius` | `blockRadius` | - | | `@skeleton-title-height` | `titleHeight` | - | | `@skeleton-color` | `gradientFromColor` | - | | `@skeleton-to-color` | `gradientToColor` | - | | `@skeleton-paragraph-margin-top` | `paragraphMarginTop` | - | | `@skeleton-paragraph-li-height` | `paragraphLiHeight` | - | | `@skeleton-paragraph-li-margin-top` | - | Deprecated for style change | ### Slider | Less variables | Component Token | Note | | --- | --- | --- | | `@slider-margin` | - | Could be customized with `className` or `style` | | `@slider-rail-background-color` | `railBg` | - | | `@slider-rail-background-color-hover` | `railHoverBg` | - | | `@slider-track-background-color` | `trackBg` | - | | `@slider-track-background-color-hover` | `trackHoverBg` | - | | `@slider-handle-border-width` | `handleLineWidth` | - | | `@slider-handle-background-color` | - | Deprecated | | `@slider-handle-color` | `handleColor` | - | | `@slider-handle-color-hover` | `handleActiveColor` | - | | `@slider-handle-color-focus` | `handleActiveColor` | - | | `@slider-handle-color-focus-shadow` | - Deprecated | | `@slider-handle-color-tooltip-open` | `handleActiveColor` | - | | `@slider-handle-size` | `handleSize` | - | | `@slider-handle-margin-top` | - | Deprecated | | `@slider-handle-margin-left` | - | Deprecated | | `@slider-handle-shadow` | - | Deprecated | | `@slider-dot-border-color` | `dotBorderColor` | - | | `@slider-dot-border-color-active` | `dotActiveBorderColor` | - | | `@slider-disabled-color` | `trackBgDisabled` | - | | `@slider-disabled-background-color` | - | Deprecated | ### Spin | Less variables | Component Token | Note | | --- | --- | --- | | `@spin-dot-size-sm` | `dotSizeSM` | - | | `@spin-dot-size` | `dotSize` | - | | `@spin-dot-size-lg` | `dotSizeLG` | - | ### Statistic | Less variables | Component Token | Note | | --- | --- | --- | | `@statistic-title-font-size` | `titleFontSize` | - | | `@statistic-content-font-size` | `contentFontSize` | - | | `@statistic-font-family` | `fontFamily` | GlobalToken | ### Step | Less variables | Component Token | Note | | --- | --- | --- | | `@process-tail-color` | `colorSplit` | GlobalToken | | `@steps-nav-arrow-color` | `navArrowColor` | - | | `@steps-background` | `colorBgContainer` | - | | `@steps-icon-size` | `iconSize` | - | | `@steps-icon-custom-size` | `customIconSize` | - | | `@steps-icon-custom-top` | `customIconTop` | - | | `@steps-icon-custom-font-size` | `customIconFontSize` | - | | `@steps-icon-top` | `iconTop` | - | | `@steps-icon-font-size` | `iconFontSize` | - | | `@steps-icon-margin` | - | Deprecated | | `@steps-title-line-height` | `titleLineHeight` | - | | `@steps-small-icon-size` | `iconSizeSM` | - | | `@steps-small-icon-margin` | - | Deprecated | | `@steps-dot-size` | `dotSize` | - | | `@steps-dot-top` | - | Deprecated | | `@steps-current-dot-size` | `dotCurrentSize` | - | | `@steps-description-max-width` | `descriptionMaxWidth` | - | | `@steps-nav-content-max-width` | `stepsNavContentMaxWidth` | - | | `@steps-vertical-icon-width` | `iconSize` | - | | `@steps-vertical-tail-width` | - | Deprecated | | `@steps-vertical-tail-width-sm` | - | Deprecated | ### Switch | Less variables | Component Token | Note | | --- | --- | --- | | `@switch-height` | `trackHeight` | - | | `@switch-sm-height` | `trackHeightSM` | - | | `@switch-min-width` | `trackMinWidth` | - | | `@switch-sm-min-width` | `trackMinWidthSM` | - | | `@switch-disabled-opacity` | `opacityLoading` | Global Token | | `@switch-color` | `colorPrimary` | Global Token | | `@switch-bg` | `handleBg` | - | | `@switch-shadow-color` | `handleShadow` | Control `box-shadow`, not only shadow color | | `@switch-padding` | `trackPadding` | - | | `@switch-inner-margin-min` | `innerMinMargin` | - | | `@switch-inner-margin-max` | `innerMaxMargin` | - | | `@switch-sm-inner-margin-min` | `innerMinMarginSM` | - | | `@switch-sm-inner-margin-max` | `innerMaxMarginSM` | - | ### Table | Less variables | Component Token | Note | | --- | --- | --- | | `@table-bg` | `colorBgContainer` | Global Token | | `@table-header-bg` | `headerBg` | - | | `@table-header-color` | `headerColor` | - | | `@table-header-sort-bg` | `headerSortActiveBg` | - | | `@table-body-sort-bg` | `bodySortActiveBg` | - | | `@table-row-hover-bg` | `rowHoverBg` | - | | `@table-selected-row-color` | `colorText` | Global Token | | `@table-selected-row-bg` | `rowSelectedBg` | - | | `@table-body-selected-sort-bg` | - | Deprecated, same as `rowSelectedBg` | | `@table-selected-row-hover-bg` | `rowSelectedHoverBg` | - | | `@table-expanded-row-bg` | `rowExpandedBg` | - | | `@table-padding-vertical` | `cellPaddingBlock` | - | | `@table-padding-horizontal` | `cellPaddingInline` | - | | `@table-padding-vertical-md` | `cellPaddingBlockMD` | - | | `@table-padding-horizontal-md` | `cellPaddingInlineMD` | - | | `@table-padding-vertical-sm` | `cellPaddingBlockSM` | - | | `@table-padding-horizontal-sm` | `cellPaddingInlineSM` | - | | `@table-border-color` | `borderColor` | - | | `@table-border-radius-base` | `headerBorderRadius` | - | | `@table-footer-bg` | `footerBg` | - | | `@table-footer-color` | `footerColor` | - | | `@table-header-bg-sm` | - | Deprecated, same as `headerBg` | | `@table-font-size` | `cellFontSize` | - | | `@table-font-size-md` | `cellFontSizeMD` | - | | `@table-font-size-sm` | `cellFontSizeSM` | - | | `@table-header-cell-split-color` | `headerSplitColor` | - | | `@table-header-sort-active-bg` | `headerSortHoverBg` | Misused in v4, and used as hover bg actually | | `@table-fixed-header-sort-active-bg` | `fixedHeaderSortActiveBg` | - | | `@table-header-filter-active-bg` | `headerFilterHoverBg` | - | | `@table-filter-btns-bg` | - | Deprecated, same as `filterDropdownBg` | | `@table-filter-dropdown-bg` | `filterDropdownBg` | - | | `@table-expand-icon-bg` | `expandIconBg` | - | | `@table-selection-column-width` | `selectionColumnWidth` | - | | `@table-sticky-scroll-bar-bg` | `stickyScrollBarBg` | - | | `@table-sticky-scroll-bar-radius` | `stickyScrollBarBorderRadius` | - | ### Tabs | Less variables | Component Token | Note | | --- | --- | --- | | `@tabs-card-head-background` | `cardBg` | - | | `@tabs-card-height` | `cardHeight` | - | | `@tabs-card-active-color` | `itemSelectedColor` | - | | `@tabs-card-horizontal-padding` | `cardPadding` | - | | `@tabs-card-horizontal-padding-sm` | `cardPaddingSM` | - | | `@tabs-card-horizontal-padding-lg` | `cardPaddingLG` | - | | `@tabs-title-font-size` | `titleFontSize` | - | | `@tabs-title-font-size-lg` | `titleFontSizeLG` | - | | `@tabs-title-font-size-sm` | `titleFontSizeSM` | - | | `@tabs-ink-bar-color` | `inkBarColor` | - | | `@tabs-bar-margin` | `horizontalMargin` | - | | `@tabs-horizontal-gutter` | `horizontalItemGutter` | - | | `@tabs-horizontal-margin` | `horizontalItemMargin` | - | | `@tabs-horizontal-margin-rtl` | `horizontalItemMarginRTL` | - | | `@tabs-horizontal-padding` | `horizontalItemPadding` | - | | `@tabs-horizontal-padding-lg` | `horizontalItemPaddingLG` | - | | `@tabs-horizontal-padding-sm` | `horizontalItemPaddingSM` | - | | `@tabs-vertical-padding` | `verticalItemPadding` | - | | `@tabs-vertical-margin` | `verticalItemMargin` | - | | `@tabs-scrolling-size` | - | Deprecated | | `@tabs-highlight-color` | `itemSelectedColor` | - | | `@tabs-hover-color` | `itemHoverColor` | - | | `@tabs-active-color` | `itemActiveColor` | - | | `@tabs-card-gutter` | `cardGutter` | - | | `@tabs-card-tab-active-border-top` | - | Deprecated | ### Tag | Less variables | Component Token | Note | | --- | --- | --- | | `@tag-border-radius` | `borderRadiusSM` | Global Token | | `@tag-default-bg` | `defaultBg` | - | | `@tag-default-color` | `defaultColor` | - | | `@tag-font-size` | `fontSizeSM` | Global Token | | `@tag-line-height` | `lineHeightSM` | Global Token | ### Timeline | Less variables | Component Token | Note | | --- | --- | --- | | `@timeline-width` | `tailWidth` | `tailWidth` is a number without units, `@timeline-width` with units | | `@timeline-color` | `tailColor` | - | | `@timeline-dot-border-width` | `dotBorderWidth` | - | | `@timeline-dot-color` | - | Deprecated | | `@timeline-dot-bg` | `dotBg` | - | | `@timeline-item-padding-bottom` | `itemPaddingBottom` | - | ### Tooltip | Less variables | Component Token | Note | | --- | --- | --- | | `@tooltip-max-width` | - | Can be directly modified by `className` or `style` | | `@tooltip-color` | `colorTextLightSolid` | Global Token | | `@tooltip-bg` | `colorBgSpotlight` | Global Token | | `@tooltip-arrow-width` | `sizePopupArrow` | Global Token | | `@tooltip-distance` | `marginXXS` | Global Token | | `@tooltip-arrow-color` | - | same as `@tooltip-bg`, Deprecated | | `@tooltip-border-radius` | `borderRadius` | Global Token | ### Transfer | Less variables | Component Token | Note | | --- | --- | --- | | `@transfer-header-height` | `headerHeight` | - | | `@transfer-item-height` | `itemHeight` | - | | `@transfer-disabled-bg` | `colorBgContainerDisabled` | Global Token | | `@transfer-list-height` | `listHeight` | - | | `@transfer-item-hover-bg` | `controlItemBgHover` | Global Token | | `@transfer-item-selected-hover-bg` | `controlItemBgActiveHover` | Global Token | | `@transfer-item-padding-vertical` | `itemPaddingBlock` | - | | `@transfer-list-search-icon-top` | - | Deprecated | ### Tree | Less variables | Component Token | Note | | --- | --- | --- | | `@tree-bg` | `colorBgContainer` | Global Token | | `@tree-title-height` | `titleHeight` | - | | `@tree-child-padding` | - | Deprecated | | `@tree-directory-selected-color` | `directoryNodeSelectedColor` | - | | `@tree-directory-selected-bg` | `directoryNodeSelectedBg` | - | | `@tree-node-hover-bg` | `nodeHoverBg` | - | | `@tree-node-selected-bg` | `nodeSelectedBg` | - | ### Typography | Less variables | Component Token | Note | | --- | --- | --- | | `@typography-title-font-weight` | `fontWeightStrong` | Global Token | | `@typography-title-margin-top` | `titleMarginTop` | - | | `@typography-title-margin-bottom` | `titleMarginBottom` | - | ### Upload | Less variables | Component Token | Note | | --- | --- | --- | | `@upload-actions-color` | `actionsColor` | - | --- Title: Ant Design of React URL: https://ant.design/docs/react/introduce --- Following the Ant Design specification, we developed a React UI library `antd` () that contains a set of high quality components and demos for building rich, interactive user interfaces.
    +
    --- ## ✨ Features - 🌈 Enterprise-class UI designed for web applications. - 📦 A set of high-quality React components out of the box. - 🛡 Written in TypeScript with predictable static types. - ⚙️ Whole package of design resources and development tools. - 🌍 Internationalization support for dozens of languages. - 🎨 Powerful theme customization in every detail. ## Environment Support - Modern browsers - Server-side Rendering - [Electron](https://www.electronjs.org/) | [Edge](https://godban.github.io/browsers-support-badges/)
    Edge | [Firefox](https://godban.github.io/browsers-support-badges/)
    Firefox | [Chrome](https://godban.github.io/browsers-support-badges/)
    Chrome | [Safari](https://godban.github.io/browsers-support-badges/)
    Safari | [Opera](https://godban.github.io/browsers-support-badges/)
    Opera | [Electron](https://godban.github.io/browsers-support-badges/)
    Electron | | --- | --- | --- | --- | --- | --- | | Edge | last 2 versions | last 2 versions | last 2 versions | last 2 versions | last 2 versions | Polyfills are needed for IE browsers. We recommend [@babel/preset-env](https://babeljs.io/docs/en/babel-preset-env) for it. You can set `targets` config if you are using [umi](https://umijs.org/). > Dropped support of IE8 after `antd@2.0`. Dropped support of React 15 and IE9/10 after `antd@4.0`. Dropped support of IE after `antd@5.0`. ## Version - Stable: [![npm package](https://img.shields.io/npm/v/antd.svg?style=flat-square)](https://www.npmjs.org/package/antd) You can subscribe to this feed for new version notifications: https://github.com/ant-design/ant-design/releases.atom ## Installation ### Using npm or yarn or pnpm or bun **We recommend using [npm](https://www.npmjs.com/) or [yarn](https://github.com/yarnpkg/yarn/) or [pnpm](https://pnpm.io/) or [bun](https://bun.sh/) to install**, it not only makes development easier, but also allow you to take advantage of the rich ecosystem of Javascript packages and tooling. If you are in a bad network environment, you can try other registries and tools like [cnpm](https://github.com/cnpm/cnpm). ### Import in Browser Add `script` and `link` tags in your browser and use the global variable `antd`. We provide `antd.js` and `antd.min.js` `reset.css` under [dist](https://unpkg.com/browse/antd@5.0.0/dist/) folder in antd's npm package. You can also download these files directly from [![CDNJS](https://img.shields.io/cdnjs/v/antd.svg?style=flat-square)](https://cdnjs.com/libraries/antd), [![](https://data.jsdelivr.com/v1/package/npm/antd/badge)](https://www.jsdelivr.com/package/npm/antd) or [unpkg](https://unpkg.com/antd/dist). > **We strongly discourage loading the entire files** this will add bloat to your application and make it more difficult to receive bugfixes and updates. Antd is intended to be used in conjunction with a build tool, such as [webpack](https://webpack.github.io/), which will make it easy to import only the parts of antd that you are using. > Note: You should import `react`, `react-dom`, `dayjs` before using `antd.js`. ## Usage ```jsx import React from 'react'; import { DatePicker } from 'antd'; const App = () => { return ; }; export default App; ``` ### Use modularized antd `antd` supports ES modules tree shaking by default. ### TypeScript `antd` provides a built-in ts definition, don't install `@types/antd`. ## Links - [Home page](/) - [China Mirrors](https://github.com/ant-design/ant-design/issues/25661) - [Components](/components/overview) - [Change Log](/changelog) - [rc-components](https://react-component.github.io/) - [Ant Design Icons](https://github.com/ant-design/ant-design-icons) - [Ant Design Colors](https://github.com/ant-design/ant-design-colors) - [🆕 Ant Design X](https://x.ant.design/index-cn) - [Ant Design Pro](https://pro.ant.design/) - [Pro Components](https://procomponents.ant.design) - [Ant Design Mobile](https://mobile.ant.design) - [Ant Design Mini](https://mini.ant.design) - [Ant Design Charts](https://charts.ant.design) - [Ant Design Web3](https://web3.ant.design) - [Landing Pages](https://landing.ant.design) - [Ant Motion](https://motion.ant.design) - [Scaffold Market](https://scaffold.ant.design) - [Developer Instruction](https://github.com/ant-design/ant-design/wiki/Development) - [Versioning Release Note](https://github.com/ant-design/ant-design/wiki/%E8%BD%AE%E5%80%BC%E8%A7%84%E5%88%99%E5%92%8C%E7%89%88%E6%9C%AC%E5%8F%91%E5%B8%83%E6%B5%81%E7%A8%8B) - [FAQ](/docs/react/faq) - [CodeSandbox Template](https://u.ant.design/codesandbox-repro) for bug reports - [Awesome Ant Design](https://github.com/websemantics/awesome-ant-design) - [Customize Theme](/docs/react/customize-theme) - [How to Apply for Being A Collaborator](https://github.com/ant-design/ant-design/wiki/Collaborators#how-to-apply-for-being-a-collaborator) ## Non-React Implementations React is used to encapsulate a library of components which embody our design language. We welcome the community to implement our design system [in other front-end frameworks](/docs/spec/introduce#front-end-implementation) of their choice. ## Companies using antd Ant Design is widely used for building enterprise-level websites both domestically and internationally. You can refer to wappalyzer for reference data. If your company or product uses Ant Design, let us know [here](https://github.com/ant-design/ant-design/issues/477)! ## Contributing Please read our [CONTRIBUTING.md](https://github.com/ant-design/ant-design/blob/master/.github/CONTRIBUTING.md) first. If you'd like to help us improve antd, just create a [Pull Request](https://github.com/ant-design/ant-design/pulls). Feel free to report bugs and issues [here](https://new-issue.ant.design/). > If you're new to posting issues, we ask that you read [_How To Ask Questions The Smart Way_](https://www.catb.org/~esr/faqs/smart-questions.html) and [How to Ask a Question in Open Source Community](https://github.com/seajs/seajs/issues/545) and [How to Report Bugs Effectively](https://www.chiark.greenend.org.uk/~sgtatham/bugs.html) prior to posting. Well written bug reports help us help you! ## Need Help? For questions on how to use antd, please post questions to [GitHub Discussions](https://github.com/ant-design/ant-design/discussions) using the `Q&A` tag or [Stack Overflow](https://stackoverflow.com/questions/tagged/antd) using the `antd` tag. As always, we encourage experienced users to help those who are not familiar with `antd`! --- Title: Advanced URL: https://ant.design/docs/react/i18n --- The default language of `antd` is currently English. If you wish to use other languages, follow the instructions below. ## ConfigProvider `antd` provides a React Component [ConfigProvider](/components/config-provider) for configuring antd locale text globally. ```jsx import { ConfigProvider } from 'antd'; import frFR from 'antd/locale/fr_FR'; return ( ); ``` You can see the complete configuration here: [ConfigProvider](/components/config-provider). Note: `fr_FR` is the filename, the following table also follows the same rules. The following languages are currently supported: ### Supported languages: | Language | Filename | | ------------------------ | -------- | | Arabic | ar_EG | | Azerbaijani | az_AZ | | Bulgarian | bg_BG | | Bangla (Bangladesh) | bn_BD | | Belarusian | by_BY | | Catalan | ca_ES | | Czech | cs_CZ | | Danish | da_DK | | German | de_DE | | Greek | el_GR | | English (United Kingdom) | en_GB | | English | en_US | | Spanish | es_ES | | Basque | eu_ES | | Estonian | et_EE | | Persian | fa_IR | | Finnish | fi_FI | | French (Belgium) | fr_BE | | French (Canada) | fr_CA | | French (France) | fr_FR | | Irish (Ireland) | ga_IE | | Galician (Spain) | gl_ES | | Hebrew | he_IL | | Hindi | hi_IN | | Croatian | hr_HR | | Hungarian | hu_HU | | Armenian | hy_AM | | Indonesian | id_ID | | Italian | it_IT | | Icelandic | is_IS | | Japanese | ja_JP | | Georgian | ka_GE | | Kurdish (Kurmanji) | kmr_IQ | | Kannada | kn_IN | | Kazakh | kk_KZ | | Khmer | km_KH | | Korean | ko_KR | | Lithuanian | lt_LT | | Latvian | lv_LV | | Macedonian | mk_MK | | Malayalam (India) | ml_IN | | Mongolian | mn_MN | | Malay (Malaysia) | ms_MY | | Burmese | my_MM | | Norwegian | nb_NO | | Nepali | ne_NP | | Dutch (Belgium) | nl_BE | | Dutch | nl_NL | | Polish | pl_PL | | Portuguese (Brazil) | pt_BR | | Portuguese | pt_PT | | Romanian | ro_RO | | Russian | ru_RU | | Sinhalese / Sinhala | si_LK | | Slovak | sk_SK | | Serbian | sr_RS | | Slovenian | sl_SI | | Swedish | sv_SE | | Tamil | ta_IN | | Thai | th_TH | | Turkish | tr_TR | | Turkmen | tk_TK | | Urdu (Pakistan) | ur_PK | | Ukrainian | uk_UA | | Uzbek(latn) | uz_UZ | | Vietnamese | vi_VN | | Chinese (Simplified) | zh_CN | | Chinese (Traditional) | zh_HK | | Chinese (Traditional) | zh_TW | See more usage at [ConfigProvider](/components/config-provider). ## Adding new language If your language is not in above list, feel free to create a locale package based on the [en_US](https://github.com/ant-design/ant-design/blob/master/components/locale/en_US.ts) language pack and send us a pull request. For reference, you can refer to the pull request of adding the [Azerbaijani](https://github.com/ant-design/ant-design/pull/21387) language as a sample. Do it step by step: 1. Fork `antd` and git clone to local, switch to `feature` branch, pull it to make sure it's up-to-date, create a new branch based on `feature` branch, all work will be done in it. ```bash git clone git@github.com:/ant-design.git cd ant-design/ git remote add upstream git@github.com:ant-design/ant-design.git git checkout -b upstream/feature ``` 2. Add the language support for [@rc-component/picker](https://github.com/react-component/picker), for example [this](https://github.com/react-component/picker/blob/master/src/locale/en_US.ts). 3. Add the language support for [@rc-component/pagination](https://github.com/react-component/pagination), for example [this](https://github.com/react-component/pagination/blob/master/src/locale/en_US.ts). 4. Wait for `@rc-component/picker` and `@rc-component/pagination` to release the new version containing the above. 5. Update the `@rc-component/picker` and `@rc-component/pagination` versions in `antd` and add the remaining other necessary content for the language. for example [Azerbaijani PR](https://github.com/ant-design/ant-design/pull/21387). 6. Add a test case for the language in [index.test.tsx](https://github.com/ant-design/ant-design/blob/master/components/locale/__tests__/index.test.tsx). 7. update snapshots, you may also need to delete `node_modules`, lock files (`yarn.lock` or `package-lock.json`) and reinstall at first. ```bash npm run test -- components/locale -u ``` 8. Add the language to i18n list [docs/react/i18n.en-US.md](https://github.com/ant-design/ant-design/blob/master/docs/react/i18n.en-US.md) and [docs/react/i18n.zh-CN.md](https://github.com/ant-design/ant-design/blob/master/docs/react/i18n.zh-CN.md). 9. Watch out the CI status, and if it failed, look at the logs and make some changes until it all passes. 10. Ok, now everything is ready for review. --- Title: Basic Usage URL: https://ant.design/docs/react/getting-started --- Ant Design React is dedicated to providing a **good development experience** for programmers. Before starting, it is recommended to learn [React](https://react.dev) first, and correctly install and configure [Node.js](https://nodejs.org/) v16 or above. The official guide also assumes that you have intermediate knowledge about HTML, CSS, and JavaScript, and React. If you are just starting to learn front-end or React, it may not be the best idea to use the UI framework as your first step. Finally, if you are working in a local development environment, please refer to [Scaffolding Guide](https://u.ant.design/guide) to create a new project. --- ## Your First Example Here is a simple online codesandbox demo of an Ant Design component to show the usage of Ant Design React. ```sandpack const sandpackConfig = { autorun: true, }; import React from 'react'; import { Button, Space, DatePicker, version } from 'antd'; const App = () => (

    antd version: {version}

    ); export default App; ``` Follow the steps below to play around with Ant Design yourself: ### 1. Create a codesandbox Visit https://u.ant.design/codesandbox-repro to create a codesandbox -- don't forget to press the save button as well to create a new instance. ### 2. Use and modify an antd component Replace the contents of `index.js` with the following code. As you can see, there is no difference between antd's components and typical React components. If you have already set things up by following the [Use with create-react-app](/docs/react/use-with-create-react-app), replace the content of `/src/index.js` as follows: ```jsx import React, { useState } from 'react'; import { DatePicker, message } from 'antd'; import { createRoot } from 'react-dom/client'; import './index.css'; const App = () => { const [date, setDate] = useState(null); const [messageApi, contextHolder] = message.useMessage(); const handleChange = (value) => { messageApi.info(`Selected Date: ${value ? value.format('YYYY-MM-DD') : 'None'}`); setDate(value); }; return (
    Selected Date: {date ? date.format('YYYY-MM-DD') : 'None'}
    {contextHolder}
    ); }; createRoot(document.getElementById('root')).render(); ``` ### 3. Explore more components You can view the list of components in the side menu of the Components page, such as the [Alert](/components/alert) component. Plenty of examples are also provided in the component pages and API documentation as well. Click the "Open in Editor" icon in the first example to open an editor with source code to use out-of-the-box. Now you can import the `Alert` component into the codesandbox: ```diff - import { DatePicker, message } from 'antd'; + import { DatePicker, message, Alert } from 'antd'; ``` Now add the following jsx inside the `render` function. ```diff this.handleChange(value)} />
    - Selected Date: {date ? date.format('YYYY-MM-DD') : 'None'} +
    ``` Select a date, and you can see the effect in the preview area on the right: codesandbox screenshot OK! Now that you know the basics of using antd components, you are welcome to explore more components in the codesandbox. When reporting a bug with ant design, we also strongly recommend using codesandbox to provide a reproducible demo as well. ### 4. Next Steps During actual real-world project development, you will most likely need a development workflow consisting of `compile/build/deploy/lint/debug/` deployment. You can read the following documents on the subject or use the following scaffolds and examples provided below: - [Ant Design Pro](https://pro.ant.design/) - [create-next-app](https://github.com/ant-design/ant-design-examples/tree/main/examples/with-nextjs-inline-style) - More scaffolds at [Scaffold Market](https://scaffold.ant.design/) ## Test with Jest If you use `create-react-app` follow the instructions [here](/docs/react/use-with-create-react-app) instead. Jest does not support `esm` modules, and Ant Design uses them. In order to test your Ant Design application with Jest you have to add the following to your Jest config : ```json "transform": { "^.+\\.(ts|tsx|js|jsx)?$": "ts-jest" } ``` ## Import on Demand `antd` supports tree shaking of ES modules, so using `import { Button } from 'antd';` would drop js code you didn't use. ## Customize your Workflow If you want to customize your workflow, we recommend using [webpack](https://webpack.js.org) or [vite](https://vitejs.dev/) to build and debug code. You can try out plenty of [boilerplates](https://github.com/enaqx/awesome-react#react-tools) available in the React ecosystem. There are also some [scaffolds](https://scaffold.ant.design/) which have already been integrated into antd, so you can try and start with one of these and even contribute. --- Title: Other URL: https://ant.design/docs/react/faq --- Here are the frequently asked questions about Ant Design and antd that you should look up before you ask in the community or create a new issue. We also maintain a [FAQ issues label](http://u.ant.design/faq) for common GitHub issues. --- ## Is there a difference between `undefined` and `null` in the controlled components of `antd`? **Yes. antd will treat `undefined` as uncontrolled but `null` as controlled component which means empty value of it.** As input element, React treats both `undefined` and `null` as uncontrolled. When the `value` is converted from a valid value to `undefined` or `null`, the component is no longer controlled, which causes some unexpected cases. But in antd, `undefined` is treated as uncontrolled, and `null` is used as an explicit empty value of controlled components. To deal with some cases (e.g. `allowClear`) like clearing the `value` when the `value` is non-primitive. If you need a component controlled with the `value` valid, just set the `value` as `null`. Note: For `options` in `Select-like` components, it is **strongly recommended not** to use `undefined` and `null` as `value` in `option`. Please use `string | number` as a valid `value` in `option`. ## Can I use internal API which is not documented on the site? NOT RECOMMENDED. Internal API is not guaranteed to be compatible with future versions. It may be removed or changed in some versions. If you really need to use it, you should make sure these APIs are still valid when upgrading to a new version or just lock version for usage. ## Why API request should be strict discussion? We are cautious when adding APIs because some APIs may not be abstract enough to become historical debt. For example, when there is a need to change the way of interaction, these poor abstractions may cause breaking changes. To avoid such problems, we recommend that new features be implemented through HOCs first. ## `Select Dropdown DatePicker TimePicker Popover Popconfirm` disappears when I click another popup component inside it. How do I resolve this? This is an old bug that has been fixed since `v3.11.x`. If you're using an older version, you can use ` trigger.parentElement}>` ([API reference](/components/select/#select-props)) to render a component inside the scroll area. If you need to config this globally in your application, try ` trigger.parentElement}>` ([API reference](/components/config-provider/#api)) And make sure that parentElement is `position: relative` or `position: absolute`. Related issue: [#3487](https://github.com/ant-design/ant-design/issues/3487) [#3438](https://github.com/ant-design/ant-design/issues/3438) ## How do I modify the default theme of Ant Design? See: [customize-theme](/docs/react/customize-theme). ## How do I modify `Menu`/`Button`(etc.)'s style? While you can override a component's style, we don't recommend doing so. antd is not only a set of React components, but also a design specification as well. ## How to avoid breaking change when update version? antd will avoid breaking change in minor & patch version. You can safely do the following things: - Official demo usage - FAQ suggestion. Including codesandbox sample, marked as FAQ issue And which you should avoid doing: - Bug as feature. It will break in any other case (e.g. Use div as Tabs children) - Use magic code to realize requirement but which can be realized with normal API ## How to use other data-time lib like Moment.js? Please refer to [Use custom date library](/docs/react/use-custom-date-library). ## It doesn't work when I change `defaultValue` dynamically. The `defaultXxxx` (e.g. `defaultValue`) of `Input`/`Select`(etc...) only works on the first render. It is a specification of React. Please read [React's documentation](https://react.dev/reference/react-dom/components/input#controlling-an-input-with-a-state-variable). ## Why does modifying props in mutable way not trigger a component update? antd use shallow compare of props to optimize performance. You should always pass the new object when updating the state. Please ref [React's document](https://reactjs.org/docs/thinking-in-react.html) ## After I set the `value` of an `Input`/`Select`(etc.) component, the value cannot be changed by user's action. Try `onChange` to change `value`, and please read [React's documentation](https://react.dev/reference/react-dom/components/input#controlling-an-input-with-a-state-variable). ## Components are not vertically aligned when placed in single row. Try [Space](https://ant.design/components/space/) component to make them aligned. ## antd overrides my global styles Yes, antd is designed to help you develop a complete background application. To do so, we override some global styles for styling convenience, and currently these cannot be removed or changed. More info at https://github.com/ant-design/ant-design/issues/4331 . Alternatively, follow the instructions in [How to avoid modifying global styles?](/docs/react/customize-theme#how-to-avoid-modifying-global-styles) ## I cannot install `antd` and `antd`'s dependencies in mainland China. To potentially solve this, try [npm mirror china](https://npmmirror.com) and [cnpm](https://github.com/cnpm/cnpm). ## I set `dependencies.antd` as the git repository in `package.json`, but it doesn't work. Please install `antd` with either npm or yarn. ## `message` and `notification` is lower case, but other components are capitalized. Is this a typo? No, `message` is just a function, not a React Component, thus it is not a typo that it is in lower case. ## `antd` doesn't work well in mobile. Please check [Ant Design Mobile](http://mobile.ant.design) as a possible solution, as `antd` has not been optimized to work well on mobile. You can also try the [react-component](https://github.com/react-component/) repositories which start with 'm-' 'rn-', which are also designed for mobile. ## Does `antd` supply standalone files like 'React'? Yes, you can [import `antd` with script tag](https://ant.design/docs/react/introduce#import-in-browser), but we recommend using `npm` to import `antd`, as it is simple and easy to maintain. ## How do I extend antd's components? If you need some features which should not be included in antd, try to extend antd's component with [HOC](https://gist.github.com/sebmarkbage/ef0bf1f338a7182b6775). [more](https://medium.com/@dan_abramov/mixins-are-dead-long-live-higher-order-components-94a0d2f9e750#.eeu8q01s1) antd will have a strict discussion on the demand for new components to prevent API corruption and become [historical debt](/docs/blog/historical-debt). And it is also more inclined to provide atomic capabilities for APIs so that developers can customize the features they need more flexibly. ## How to get the definition which is not export? antd expose the basic component definitions. For the unexposed props, you can get them via the utility types provided by antd. For example: ```tsx import type { Checkbox, CheckboxProps, GetProp, GetProps, GetRef, Input } from 'antd'; // Get Props type CheckboxGroupProps = GetProps; // Get Prop type CheckboxValue = GetProp; // Get Ref type InputRef = GetRef; ``` ## Date-related components locale is not working? Please check whether you have imported dayjs locale correctly. ```jsx import dayjs from 'dayjs'; import 'dayjs/locale/zh-cn'; dayjs.locale('zh-cn'); ``` Please check whether there are two versions of dayjs installed. ```jsx npm ls dayjs ``` If you are using a mismatched version of dayjs with [antd's dayjs](https://github.com/ant-design/ant-design/blob/7dfc80504a36cf8952cd732a1d0c137a16d56fd4/package.json#L125) in your project. That would be a problem cause locale not working. ## How do I fix dynamic styles while using a Content Security Policy (CSP)? You can configure `nonce` by [ConfigProvider](/components/config-provider/#content-security-policy). ## When I set `mode` to `DatePicker`/`RangePicker`, why can I not select a year or month anymore? In a real world development, you may need a `YearPicker`, `MonthRangePicker` or `WeekRangePicker`. You are trying to add `mode` to `DatePicker`/`RangePicker` expected to implement those pickers. However, the `DatePicker`/`RangePicker` cannot be selected and the panels won't close now. - Reproduction link: https://codesandbox.io/s/dank-brook-v1csy - Same issues：[#15572](https://github.com/ant-design/ant-design/issues/15572), [#16436](https://github.com/ant-design/ant-design/issues/16436), [#11938](https://github.com/ant-design/ant-design/issues/11938), [#11735](https://github.com/ant-design/ant-design/issues/11735), [#11586](https://github.com/ant-design/ant-design/issues/11586), [#10425](https://github.com/ant-design/ant-design/issues/10425), [#11053](https://github.com/ant-design/ant-design/issues/11053) Like [the explanation](https://github.com/ant-design/ant-design/issues/11586#issuecomment-429189877) explains, this is because `` does not equal the `YearPicker`, nor is `` equal to `MonthRangePicker`. The `mode` property was added to support [showing time picker panel in DatePicker](https://github.com/ant-design/ant-design/issues/5190) in antd 3.0, which simply controls the displayed panel, and won't change the original date picking behavior of `DatePicker`/`RangePicker` (for instance you will still need to click date cell to finish selection in a `DatePicker`, whatever the `mode` is). Likewise, `disabledDate` [cannot work on year/month panels](https://github.com/ant-design/ant-design/issues/9008#issuecomment-358554118) of ``, but only on cells of date panel. :::success{title=Workaround} You can refer to [this article](https://juejin.im/post/5cf65c366fb9a07eca6968f9) or [this article](https://www.cnblogs.com/zyl-Tara/p/10197177.html), using `mode` and `onPanelChange` to encapsulate a `YearPicker` or `MonthRangePicker` for your needs. Or you can simply upgrade to [antd@4.0](https://github.com/ant-design/ant-design/issues/16911), in which we [added more XxxPickers](https://github.com/ant-design/ant-design/issues/4524#issuecomment-480576884) to meet those requirements, and `disabledDate` could be effect on those pickers too. ::: ## message/notification/Modal.confirm lost styles when set `prefixCls` on ConfigProvider? Static methods like message/notification/Modal.confirm are not using the same render tree as ` ); }; ``` --- Title: Advanced URL: https://ant.design/docs/react/customize-theme --- Ant Design allows you to customize our design tokens to satisfy UI diversity from business or brand requirements, including primary color, border radius, border color, etc. In version 5.0, we provide a new way to customize themes. Different from the less and CSS variables of the 4.x version, with CSS-in-JS, the ability of theming has also been enhanced, including but not limited to: 1. Switching theme dynamically； 2. Multiple themes； 3. Customizing theme variables for some components； 4. ... ## Basic Usage In version 5.0 we call the smallest element that affects the theme **Design Token**. By modifying the Design Token, we can present various themes or components. You can pass `theme` to `ConfigProvider` to customize theme. After migrate to V5, theme of V5 will be applied by default. :::warning `ConfigProvider` will not take effect on static methods such as `message.xxx`, `Modal.xxx`, `notification.xxx`, because in these methods, antd will dynamically create new ones through `ReactDOM.render` React entities. Its context is not the same as the context of the current code, so context information cannot be obtained. When you need context information (such as the content configured by ConfigProvider), you can use the `Modal.useModal` method to return the modal entity and the contextHolder node. Just insert it where you need to get the context, or you can use [App Component](/components/app) to simplify the problem of usingModal and other methods that need to manually implant the contextHolder. ::: ### Customize Design Token By modifying `token` property of `theme`, we can modify Design Token globally. Some tokens will affect other tokens. We call these tokens Seed Token. ```sandpack const sandpackConfig = { autorun: true, }; import { Button, ConfigProvider, Space } from 'antd'; import React from 'react'; const App: React.FC = () => ( ); export default App; ``` ### Use Preset Algorithms Themes with different styles can be quickly generated by modifying `algorithm`. Ant Design 5.0 provides three sets of preset algorithms by default: - default algorithm `theme.defaultAlgorithm` - dark algorithm `theme.darkAlgorithm` - compact algorithm `theme.compactAlgorithm` You can switch algorithms by modifying the `algorithm` property of `theme` in ConfigProvider. ```sandpack const sandpackConfig = { dark: true, }; import React from 'react'; import { Button, ConfigProvider, Input, Space, theme } from 'antd'; const App: React.FC = () => ( ); export default App; ``` ### Customize Component Token In addition to Design Token, each component will also have its own Component Token to achieve style customization capabilities for components, and different components will not affect each other. Similarly, other Design Token of components can also be overridden in this way. :::info{title=Algorithm of Component Token} By default, all component tokens can only override global token and will not be derived based on Seed Token. In version `>= 5.8.0`, component tokens support the `algorithm` property, which can be used to enable algorithm or pass in other algorithms. ::: ```sandpack import React from 'react'; import { ConfigProvider, Button, Space, Input, Divider } from 'antd'; const App: React.FC = () => ( <>
    Enable algorithm:
    Disable algorithm:
    ); export default App; ``` ### Disable Motion antd has built-in interaction animations to make enterprise-level pages more detailed. In some extreme scenarios, it may affect the performance of page interaction. If you need to turn off the animation, try setting `motion` of `token` to `false`: ```sandpack import React from 'react'; import { Checkbox, Col, ConfigProvider, Flex, Radio, Row, Switch } from 'antd'; const App: React.FC = () => { const [checked, setChecked] = React.useState(false); const timerRef = React.useRef>(); React.useEffect(() => { timerRef.current = setInterval(() => { setChecked((prev) => !prev); }, 500); return () => { if (timerRef.current) { clearInterval(timerRef.current); } }; }, []); const nodes = ( Checkbox Radio ); return (     {nodes}{nodes} ); }; export default App; ``` ## Advanced ### Switch Themes Dynamically In v5, dynamically switching themes is very simple for users, you can dynamically switch themes at any time through the `theme` property of `ConfigProvider` without any additional configuration. ```sandpack import { Button, ConfigProvider, Space, Input, ColorPicker, Divider } from 'antd'; import React from 'react'; const App: React.FC = () => { const [primary, setPrimary] = React.useState('#1677ff'); return ( <> setPrimary(color.toHexString())} /> ); } export default App; ``` ### Nested Theme By nesting `ConfigProvider` you can apply local theme to some parts of your page. Design Tokens that have not been changed in the child theme will inherit the parent theme. ```sandpack import React from 'react'; import { Button, ConfigProvider, Space } from 'antd'; const App: React.FC = () => ( ); export default App; ``` ### Consume Design Token If you want to consume the Design Token under the current theme, we provide `useToken` hook to get Design Token. ```sandpack import React from 'react'; import { Button, theme } from 'antd'; const { useToken } = theme; const App: React.FC = () => { const { token } = useToken(); return (
    Consume Design Token
    ); }; export default App; ``` ### Static consume (e.g. less) When you need token out of React life cycle, you can use static function to get them: ```jsx import { theme } from 'antd'; const { getDesignToken } = theme; const globalToken = getDesignToken(); ``` Same as ConfigProvider, `getDesignToken` could also accept a config object as `theme`: ```tsx import type { ThemeConfig } from 'antd'; import { theme } from 'antd'; import { createRoot } from 'react-dom/client'; const { getDesignToken, useToken } = theme; const config: ThemeConfig = { token: { colorPrimary: '#1890ff', }, }; // By static function const globalToken = getDesignToken(config); // By hook const App = () => { const { token } = useToken(); return null; }; // Example for rendering createRoot(document.getElementById('#app')).render( , ); ``` If you want to use in preprocess style framework like less, use less-loader for injection: ```jsx { loader: "less-loader", options: { lessOptions: { modifyVars: mapToken, }, }, } ``` Compatible package provide convert function to transform to v4 less variable. Read [this](/docs/react/migration-v5) for detail. ### Theme editor We provide tools to help users debug themes: [Theme Editor](/theme-editor) You can use this tool to freely modify Design Token to meet your theme expectations. ## Design Token In Design Token, we provide a three-layer structure that is more suitable for the design, and disassemble the Design Token into three parts: Seed Token, Map Token and Alias Token. These three groups of Tokens are not simple groupings, but a three-layer derivation relationship. Map Tokens are derived from Seed Tokens, and Alias Tokens are derived from Map Tokens. In most cases, using Seed Tokens is sufficient for custom themes. But if you need a higher degree of theme customization, you need to understand the life cycle of Design Token in antd. ### Life of Design Token ![token](https://gw.alipayobjects.com/mdn/rms_08e378/afts/img/A*uF3kTrY4InUAAAAAAAAAAAAAARQnAQ) ### Seed Token Seed Token means the origin of all design intent. For example, we can change the theme color by changing `colorPrimary`, and the algorithm inside antd will automatically calculate and apply a series of corresponding colors according to the Seed Token: ```tsx const theme = { token: { colorPrimary: '#1890ff', }, }; ``` ### Map Token Map Token is a gradient variable derived from Seed. It is recommended to implement custom Map Token through `theme.algorithm`, which can ensure the gradient relationship between Map Tokens. It can also be overridden by `theme.token` to modify the value of some map tokens individually. ```tsx const theme = { token: { colorPrimaryBg: '#e6f7ff', }, }; ``` ### Alias Token Alias Token is used to control the style of some common components in batches, which is basically a Map Token alias, or a specially processed Map Token. ```tsx const theme = { token: { colorLink: '#1890ff', }, }; ``` ### Algorithm The basic algorithm is used to expand the Seed Token into a Map Token, such as calculating a gradient color palette from a basic color, or calculating rounded corners of various sizes from a basic rounded corner. Algorithms can be used alone or in any combination, for example, dark and compact algorithms can be combined to get a dark and compact theme. ```tsx import { theme } from 'antd'; const { darkAlgorithm, compactAlgorithm } = theme; const theme = { algorithm: [darkAlgorithm, compactAlgorithm], }; ``` ## API ### Theme | Property | Description | Type | Default | | --- | --- | --- | --- | | token | Modify Design Token | `AliasToken` | - | | inherit | Inherit theme configured in upper ConfigProvider | boolean | true | | algorithm | Modify the algorithms of theme | `(token: SeedToken) => MapToken` \| `((token: SeedToken) => MapToken)[]` | `defaultAlgorithm` | | components | Modify Component Token and Alias Token applied to components | `ComponentsConfig` | - | | cssVar | CSS Variables Configuration, refer [CSS Variables](/docs/react/css-variables#api) | `boolean \| { prefix?: string; key?: string }` | false | | hashed | Component class Hash value, refer [CSS Variables](/docs/react/css-variables#disable-hash) | boolean | true | | zeroRuntime | Enable zero-runtime mode, which will not generate style at runtime | boolean | true | ### ComponentsConfig | Property | Description | Type | Default | | --- | --- | --- | --- | | `Component` (Can be any antd Component name like `Button`) | Modify Component Token or override Component used Alias Token | `ComponentToken & AliasToken & { algorithm: boolean \| (token: SeedToken) => MapToken` \| `((token: SeedToken) => MapToken)[]}` | - | > `algorithm` of component is `false` by default, which means tokens of component will only override global token. When it is set with `true`, the algorithm will be the same as global. You can also pass algorithm or Array of algorithm, and it will override algorithm of global. ### SeedToken ### MapToken > Inherit all SeedToken properties ### AliasToken > Inherit all SeedToken and MapToken properties ## FAQ ### Why component re-mounted when `theme` changed from `undefined` to some object or to `undefined`? In ConfigProvider, we pass context through `DesignTokenContext`. When `theme` is `undefined`, a layer of Provider will not be set, so React VirtualDOM structure changes from scratch or from existence to nothing, causing components to be re-mounted. Solution: Replace `undefined` with an empty object `{}`. --- Title: Advanced URL: https://ant.design/docs/react/css-variables --- Since `5.12.0`, Ant Design 5.x enabled CSS variables again. Unlike 4.x, this time we have integrated the capabilities of CSS-in-JS, and all Design Tokens have been included in the management scope of CSS variables. > Currently, the CSS variable mode has been globally enabled on the official website. ## When to Use CSS variable mode brings two important improvements to Ant Design's styling capabilities: 1. The styles of the same component under different themes can be shared, reducing the total size of the styles 2. When switching themes, there is no need to re-serialize the styles, which improves the performance of theme switching Therefore, if your application depends on Ant Design's theme capabilities, we strongly recommend that you enable the CSS variable mode. ## Quick Start To enable CSS variable mode, use the `cssVar` configuration in the `theme` property of ConfigProvider. This configuration will be inherited, so if you want to enable CSS variable mode globally, you only need to configure it in the root of your application. :::warning CSS variable mode requires a unique key for each theme to ensure style isolation. In React 18, we use `useId` to generate unique keys by default, so you don't have to worry about this issue in React 18. But in React 17 or 16, you need to manually set a unique key for each theme, otherwise the themes will be mixed up. ::: ```tsx // React 18 // React 17 or 16 ``` After enabling it, you can see that some specific values in the antd component styles have been replaced with CSS variables: ![image](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*p5NrRJmUNHgAAAAAAAAAAAAADrJ8AQ/original) ## Advanced ### Disable Hash Hash is one of the features since Ant Design 5.0. Its function is to calculate a unique hash value for each theme, and use it in the class of the component to isolate the theme style. However, after enabling CSS variables, the component styles of the same antd version will not change with the token —— because we use CSS variables to fill in the dynamic parts of the styles. So if there is only one version of antd in your application, you can choose to disable hash to further reduce the total size of the styles: ```tsx ``` By the way, we strongly recommend using [extractStyle](/docs/react/server-side-rendering) to extract static styles, which will bring a certain amount of performance improvement to the application. ### Customize Theme With CSS variable mode, the method of modifying the theme is the same as before, refer to [Customize Theme](/docs/react/customize-theme). ## API `cssVar` configuration: | Properties | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | prefix | Prefix of CSS Variables, same as `prefixCls` of ConfigProvider by default | string | `ant` | 5.12.0 | | key | The unique key of theme. Automatically set by `useId` in React 18, but need to be set manually in React 17 or 16 | string | `useId` in React 18 | 5.12.0 | --- Title: Other URL: https://ant.design/docs/react/contributing --- The following is a set of guidelines for contributing to Ant Design. Please spend several minutes reading these guidelines before you create an issue or pull request. ## Code of Conduct We have adopted a [Code of Conduct](https://github.com/ant-design/ant-design/blob/master/CODE_OF_CONDUCT.md) that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated. ## Open Development All work on Ant Design happens directly on [GitHub](https://github.com/ant-design). Both core team members and external contributors send pull requests which go through the same review process. ## Branch Organization According to our [release schedule](/changelog#release-schedule), we maintain two branches, `master` and `feature`. If you send a bugfix pull request, please do it against the `master` branch, if it's a feature pull request, please do it against the `feature` branch. ## Bugs We are using [GitHub Issues](https://github.com/ant-design/ant-design/issues) for bug tracking. The best way to get your bug fixed is by using our [issue helper](http://new-issue.ant.design) and provide reproduction steps with this [template](https://u.ant.design/codesandbox-repro). Before you report a bug, please make sure you've searched existing issues, and read our [FAQ](/docs/react/faq). ## Proposing a Change If you intend to change the public API or introduce new feature, we also recommend you use our [issue helper](http://new-issue.ant.design) to create a feature request issue. If you want to help on new API, please reference [API Naming Rules](https://github.com/ant-design/ant-design/wiki/API-Naming-rules) to name it. ## Your First Pull Request Working on your first Pull Request? You can learn how from this free video series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github) To help you get your feet wet and get you familiar with our contribution process, we have a list of [good first issues](https://github.com/ant-design/ant-design/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) that contain bugs or small features that have a relatively limited scope. This is a great place to get started. If you decide to fix an issue, please be sure to check the comment thread in case somebody is already working on a fix. If nobody is working on it at the moment, please leave a comment stating that you intend to work on it so other people don't accidentally duplicate your effort. If somebody claims an issue but doesn't follow up for more than two weeks, it's fine to take over it but you should still leave a comment. ## Sending a Pull Request The core team is monitoring for pull requests. We will review your pull request and either merge it, request changes to it, or close it with an explanation. **Before submitting a pull request**, please make sure the following is done: 1. Fork the repository and create your branch from the [correct branch](#branch-organization). 2. Run `npm install` in the repository root. 3. If you've fixed a bug or added code that should be tested, add tests! 4. Ensure the test suite passes (npm run test). Tip: `npm test -- --watch TestName` is helpful in development. 5. Run `npm test -- -u` to update the [jest snapshots](https://jestjs.io/docs/snapshot-testing) and commit these changes as well (if there are any updates). 6. Ensure the UI change passes `npm run test:image`, Run `npm run test:image -- -u` to update UI snapshots and commit these changes as well (if there are any updates), **UI test base on [Docker](https://docs.docker.com/get-docker/), need download the corresponding installation according to the platform** 7. Make sure your code lints (npm run lint). Tip: Lint runs automatically when you `git commit` (Use [Git Hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks)). 8. Finally, please make sure that all GitHub CI checks pass, if they fail, you can click `detail` to enter the details to view the reason. Sending a Pull Request to [react-component](https://github.com/react-component/): Since antd's components are based on react-component, sometimes you may need to send pull request to the corresponding react-component repository. If it's a bugfix pull request, after it's merged, the core team will release a patch release for that component as soon as possible, then you only need to reinstall antd in your project to get the latest patch release. If it's a feature pull request, after it's merged, the core team will release a minor release, then you need raise another pull request to [Ant Design](https://github.com/ant-design/ant-design/) to update dependencies, document and TypeScript interfaces (if needed). ## Development Workflow `npm` or `yarn` are recommended as package management tools. After you clone the antd code and use following commands to install dependencies: You can also run the following common commands: ### Run locally Runs Ant Design website locally. ### Checks the code style ### Run test runs the complete test suite. (Make sure the `NODE_ENV` environment variable is unset, or it may causing some problems.) ### Compile compiles TypeScript code to the `lib` and `es` directory. ### Build creates UMD build of antd. ## Development Tools - VSCode plugin for CSS in JS: https://marketplace.visualstudio.com/items?itemName=shezhangzhang.antd-design-token - Ant Design cheatsheet in VS Code: https://github.com/fi3ework/vscode-antd-rush ## Being a collaborator If you are an active contributor and are willing to work with Ant Design Team in our opensource workflow, you can [apply to be a outside collaborator](https://github.com/ant-design/ant-design/wiki/Collaborators#how-to-apply-for-being-a-collaborator). You can also refer to the following contribution guide to become an antd contributor: - [How to Grow as a Collaborator](/docs/blog/to-be-collaborator) --- Title: Advanced URL: https://ant.design/docs/react/compatible-style --- ### Default Style Compatibility Ant Design supports the [last 2 versions of modern browsers](https://browsersl.ist/#q=defaults). If you need to be compatible with legacy browsers, please perform downgrade processing according to actual needs: | Feature | antd version | Compatibility | Minimum Chrome Version | Compatibility workaround | | --- | --- | --- | --- | --- | | [:where Selector](https://developer.mozilla.org/en-US/docs/Web/CSS/:where) | `>=5.0.0` | [caniuse](https://caniuse.com/?search=%3Awhere) | Chrome 88 | `` | | [CSS Logical Properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Logical_Properties) | `>=5.0.0` | [caniuse](https://caniuse.com/css-logical-props) | Chrome 89 | `` | If you need to support older browsers, please use [StyleProvider](https://github.com/ant-design/cssinjs#styleprovider) for degradation handling according to your actual requirements. ## `:where` in selector - antd version: `>=5.0.0` - MDN: [:where](https://developer.mozilla.org/en-US/docs/Web/CSS/:where) - Browser Compatibility: [caniuse](https://caniuse.com/?search=%3Awhere) - Minimum Chrome Version Supported: 88 - Default Enabled: Yes The CSS-in-JS feature of Ant Design uses the ":where" selector by default to lower the CSS selector specificity, reducing the additional cost of adjusting custom styles when upgrading for users. However, the compatibility of the ":where" syntax is relatively poor in older browsers ([compatibility](https://developer.mozilla.org/en-US/docs/Web/CSS/:where#browser_compatibility)). In certain scenarios, if you need to support older browsers, you can use `@ant-design/cssinjs` to disable the default lowering of specificity (please ensure version consistency with antd). ```tsx import { StyleProvider } from '@ant-design/cssinjs'; // Config `hashPriority` to `high` instead of default `low` // Which will remove `:where` wrapper export default () => ( ); ``` It will turn `:where` to class selector: ```diff -- :where(.css-bAMboO).ant-btn { ++ .css-bAMboO.ant-btn { color: #fff; } ``` Note: After turning off the `:where` downgrade, you may need to manually adjust the priority of some styles. Or you can **use PostCSS plugin** to raise application css selector priority. PostCSS provides many plugins can help on this. e.g: - [postcss-scopify](https://www.npmjs.com/package/postcss-scopify) - [postcss-increase-specificity](https://www.npmjs.com/package/postcss-increase-specificity) - [postcss-add-root-selector](https://www.npmjs.com/package/postcss-add-root-selector) Raise priority through plugin: ```diff -- .my-btn { ++ #root .my-btn { background: red; } ``` ## CSS Logical Properties - antd version: `>=5.0.0` - MDN：[CSS Logical Properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Logical_Properties) - Browser Compatibility: [caniuse](https://caniuse.com/css-logical-props) - Minimum Chrome Version Supported: 89 - Default Enabled: Yes To unify LTR and RTL styles, Ant Design uses CSS logical properties. For example, the original `margin-left` is replaced by `margin-inline-start`, so that it is the starting position spacing under both LTR and RTL. If you need to be compatible with older browsers, you can configure `transformers` through the `StyleProvider` of `@ant-design/cssinjs`: ```tsx import { legacyLogicalPropertiesTransformer, StyleProvider } from '@ant-design/cssinjs'; // `transformers` provides a way to transform CSS properties export default () => ( ); ``` When toggled, styles will downgrade CSS logical properties: ```diff .ant-modal-root { -- inset: 0; ++ top: 0; ++ right: 0; ++ bottom: 0; ++ left: 0; } ``` ## `@layer` - antd version: `>=5.17.0` - MDN：[CSS @layer](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) - Browser Compatibility: [caniuse](https://caniuse.com/css-at-rule-layer) - Minimum Chrome Version Supported: 99 - Default Enabled: No Ant Design supports configuring `@layer` for unified css priority downgrade since `5.17.0`. After the downgrade, the style of antd will always be lower than the default CSS selector priority, so that users can override the style (please be sure to check the browser compatibility of `@layer`).When enable `layer`, the child element **must** wrap `ConfigProvider` to update the icon-related styles: ```tsx import { StyleProvider } from '@ant-design/cssinjs'; import { ConfigProvider } from 'antd'; export default () => ( ); ``` antd styles will be encapsulated in `@layer` to lower the priority: ```diff ++ @layer antd { :where(.css-bAMboO).ant-btn { color: #fff; } ++ } ``` ## autoPrefixer - antd version: `>=6.0.0` - Browser Compatibility: Automatically adds browser prefixes for wider browser support - Default Enabled: No Some styles rely on browser prefixes for compatibility. The `autoPrefixer` transformer can automatically add browser prefixes to styles, ensuring they work properly across different browsers. ```tsx | pure import { autoPrefixTransformer, StyleProvider } from '@ant-design/cssinjs'; export default () => ( ); ``` The final transformed styles: ```diff .sample-box { -- user-select: none; ++ -webkit-user-select: none; ++ -moz-user-select: none; ++ -ms-user-select: none; ++ user-select: none; } ``` ## Rem Adaptation In responsive web development, there is a need for a convenient and flexible way to achieve page adaptation and responsive design. The `px2remTransformer` transformer can quickly and accurately convert pixel units in style sheets to rem units relative to the root element (HTML tag), enabling the implementation of adaptive and responsive layouts. ```tsx import { px2remTransformer, StyleProvider } from '@ant-design/cssinjs'; const px2rem = px2remTransformer({ rootValue: 32, // 32px = 1rem; @default 16 }); export default () => ( ); ``` The resulting transformed styles: ```diff .px2rem-box { - width: 400px; + width: 12.5rem; background-color: green; - font-size: 32px; + font-size: 1rem; border: 10PX solid #f0f; } @media only screen and (max-width: 600px) { .px2rem-box { background-color: red; - margin: 10px; + margin: 0.3125rem; } } ``` ### Options | Parameter | Description | Type | Default | | --- | --- | --- | --- | | rootValue | Font size of the root element | `number` | 16 | | precision | Decimal places for the converted value | `number` | 5 | | mediaQuery | Whether to convert px in media queries | `boolean` | false | For more details, please refer to: [px2rem.ts#Options](https://github.com/ant-design/cssinjs/blob/master/src/transformers/px2rem.ts) ## Shadow DOM Usage Since ` ``` #### ✅ Correct ```html ``` --- Title: Advanced URL: https://ant.design/docs/react/common-props --- > Tips: The following generic properties apply to most antd components; those not supported are described separately. | Property | Description | Type | Default | | ------------- | ----------------------------- | ------------- | ------- | | style | The additional style | CSSProperties | - | | className | The additional css class | string | - | | rootClassName | ClassName on the root element | string | - | --- Title: Pain of static methods URL: https://ant.design/docs/blog/why-not-static --- > `message.success` is working well, why do you warn me to use hooks? antd is getting worse and worse, goodbye! We've heard some complaints about hooks replacement of static methods. We know it's painful, but after years of consideration, we still decide to do a cut in v5 (yes, this discussion is even older than hooks, but there was no simple way to implement it before hooks, so we just put it aside). ## Static methods For the early JS, there already exists a simple and easy-to-use API `alert`. You can call it anytime, anywhere. And at the framework level, this kind of convenience is also fascinating. A common example is that use `message.error` to display an error message on the screen when the ajax request fails in Redux: Fetch Failed But from the perspective of data flow, this actually couples UI and data layer. It just looks like it doesn't directly depend on the UI context when it's called, so it looks harmless. And for the perspective of testing, this kind of coupling also makes the test complicated. ### Pain of context lost Call static methods in the function, although it looks like there is a context. But in fact, static methods will not consume the context, it will be independent of the current React lifecycle, so the content obtained through Context is actually nothing: ```tsx const Context = React.createContext('default'); const MyContent = () => React.useContext(Context); const Wrapper = () => { React.useEffect(() => { // Static function is out of context. // We can only get `default` instead of `Hello World`. message.success(); }, []); return null; }; const Demo = () => ( ); ``` Static methods are actually implemented by creating a new React instance through `ReactDOM.render`. So it's completely irrelevant to the current context. So you might think, if I configure the theme, internationalization, global configuration, etc., then these configurations will not take effect. But when I say this, you may react to: "Wait! The static method of antd internationalization is working!" Yes, but this is not really consuming the Context. We have done a very Hack implementation. When the user provides the `locale` property through ConfigProvider, we will temporarily store it in a global variable. And when the static method is called, use it to fill in: ```tsx // Sample. Not real world code. let globalLocale = null; const ConfigProvider = (props) => { if (props.locale) { globalLocale = props.locale; } // ... }; Modal.confirm = (props) => { // ... ReactDOM.render( , ); }; ``` You can easily find that this code is very fragile. Static methods don't know what the call stack is, it may be called inside or outside the ConfigProvider. Even there may be multiple ConfigProvider configurations at the same time. In this case, we cannot and cannot guarantee that the static method can correctly obtain the current configuration. When we start to support dynamic theme, this problem will become more obvious. In the theme, it is easy to encounter a mixed theme. The style of Modal, message, notification called by developers at different levels may be completely different. ### Hooks As we said above, in order to consume context, we need to know the current node position when calling the method. Therefore, in v4, we introduced the corresponding Hooks method for static methods: ```tsx const Demo = () => { const [messageApi, contextHolder] = message.useMessage(); const info = () => { messageApi.info('Hello, Ant Design!'); }; return ( <> {/* Different insert holder position will get different context */} {contextHolder} ); }; ``` You can find it's not convenient. For developers, each usage place is directly called from the past, and it becomes must to set the injected Context node. In most cases, the Context of the static method in the past only needs to pay attention to stable configurations such as internationalization and theme. So if we can have a place to put the Holder, it would be better to reuse it directly in other places. #### App Thus we provide App component in v5. This component has a DOM structure, which will add some reset styles to the sub-nodes (for example, the global style pollution that was criticized in the past version, now it will only work under App). At the same time, Modal, message, notification holder is also added in App. So after the developer adds App to the outermost layer of the application, it can be used simply in the code: ```tsx const Demo = () => { const { message } = App.useApp(); React.useEffect(() => { message.success('Hello World'); }, []); // ... }; ``` ### After All It's a bad implementation from the design perspective. But we know that static methods are so convenient and easy to use in business scenarios. Even if it has some "harmless" shortcomings, it is still worth having a place in history. So we are thinking, is there any other way to remove these side effects from the component library, but at the same time can also serve developers. For example, improve the umi antd plugin, and automatically static the top-level App instance to antd when configuring `appData`. Of course, these are just some ideas. We will continue to explore this issue in subsequent versions. --- Title: 👀 Visual Regression Testing URL: https://ant.design/docs/blog/visual-regression --- Visual Regression Testing is a software testing technique that focuses on detecting visual changes and differences in the user interface of web applications or websites. It involves capturing screenshots of web pages at different stages of development and comparing them to identify any unexpected visual regressions caused by code changes or updates. ## Baseline Screenshots The main goal of Ant Design's visual regression testing is to detect visual changes in components and avoid visual issues introduced by PR changes. We use [jest-puppeteer](https://jestjs.io/docs/puppeteer) as our testing framework. By combining Puppeteer with Jest, we take screenshots of each component demo and compare them with baseline screenshots. You can find visual regression test code in `__tests__/image.test.ts` under each component. You can run visual screenshots in the antd repository using the following command: ```bash npm run test:image # Screenshots will be saved in the imageSnapshots directory. For specific component screenshots, use: npm run test:image -- components/button ``` ## Visual Regression Solutions ### Argos Initially, we used [Argos](https://argos-ci.com/) as our visual regression testing solution. However, Argos changed their pricing strategy, and with antd triggering visual regression tests on every PR, comparing nearly 6,000 screenshots each time, the cost became unsustainable for us. ### Self-hosted We built our own visual regression testing solution using jest-puppeteer mentioned earlier. We take screenshots of each component demo using four themes: `dark`, `light`, `compact`, and `cssVar`, then upload these screenshots to [Alibaba Cloud OSS](https://www.aliyun.com/product/oss) as baseline screenshots. Using GitHub Actions for continuous integration, we automatically capture and upload screenshots to OSS whenever the base branch code changes, ensuring the baseline screenshots stay up-to-date. For branches requiring visual regression testing, we use [pixelmatch](https://github.com/mapbox/pixelmatch) to compare current screenshots with baseline screenshots. If differences are found, difference screenshots are generated, and the difference report is uploaded to OSS. Further leveraging GitHub Actions, we implement baseline screenshot comparison in PRs. If visual differences are detected, the CI uploads the difference screenshots and report to OSS, displays the visual differences in the PR, and marks it as failed, requiring developers to fix the issues. ![https://github.com/ant-design/ant-design/pull/52210#issuecomment-2567659292](https://github.com/user-attachments/assets/8a5c4e0a-3686-4b1c-aa32-930505173abe) ## Local Visual Regression Testing When developing locally and preparing to submit a PR contribution, we can run visual regression tests in advance using the following command: ```bash npm run test:visual-regression:local # Follow the prompts to select components for visual regression testing ``` ## References - For visual regression CI implementation, refer to [.github/workflows/visual-regression-\*.yml](https://github.com/search?q=repo%3Aant-design%2Fant-design%20path%3A%2F%5E%5C.github%5C%2Fworkflows%5C%2F%2F%20Visual%20Regression&type=code) - For baseline screenshot implementation, refer to [tests/shared/imageTest.tsx](https://github.com/ant-design/ant-design/blob/46a8eff/tests/shared/imageTest.tsx#L38) - For visual regression test code implementation, refer to [scripts/visual-regression](https://github.com/ant-design/ant-design/tree/46a8eff/scripts/visual-regression) --- Title: Virtual Table is here! URL: https://ant.design/docs/blog/virtual-table --- ## Preface In v4, we added a custom `components` example for Table, which replaces the default `    ` with `components.body` to achieve virtual scrolling. But many developers feedback that the virtual table in the Demo has many functions that cannot be implemented. For example, fixed columns, merged rows and columns, expandable rows, etc. So we proposed [[RFC] StaticTable for fast perf & virtual scroll support](https://github.com/ant-design/ant-design/discussions/41500) in v5. The RFC expects to provide a high-performance Table.StaticTable, which will support virtual scrolling by default. But as the development progressed, we eventually decided to implement StaticTable on the underlying `@rc-component/table`, and on the antd side, we only need to enable it with `
    `. ## TL;DR Table supports virtual scrolling by setting the `virtual` prop. At the same time, the original Table's functions can be used normally: ```tsx
    ``` ### Fixed columns ![Fixed Columns](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*V2FcS7ZAReMAAAAAAAAAAAAADrJ8AQ/original) ### Expandable ![Expandable](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*nd61R4YsknsAAAAAAAAAAAAADrJ8AQ/original) ### RowSpan & ColSpan ![Rowspan & Colspan](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*DYkYQo8tU6sAAAAAAAAAAAAADrJ8AQ/original) You can visit the [virtual list](/components/table#table-demo-virtual-list) example to experience it. ## Some details Table in antd internally uses the `@rc-component/table` component. Our virtual scrolling feature also reuses the `components` property mentioned above. Replace the middle `` with `rc-virtual-list`, which is widely used in various virtual scrolling scenarios of antd like Select and Tree. `rc-virtual-list` itself does not support horizontal scrolling, so we also added horizontal scrolling support for it in this refactoring. ### Fixed columns In v4, we refactored the fixed columns of Table into `position: sticky`. This CSS allows you to fix an element at a certain position when scrolling. So as to avoid the need to render an extra Table in v3 to achieve the fixed position effect: Sticky For overlapping fixed columns, you only need to configure different offsets: Stack Sticky We can also use this feature in virtual scrolling. Just reuse the `sticky` style to achieve the effect of fixed columns. `rc-virtual-list` only needs to provide horizontal scrolling, and does not need to care about the implementation of fixed columns. ### Expandable We will flatten the tree structure of `dataSource` through `useFlattenRecords` in `@rc-component/table`, so as to support developers' custom virtual scrolling capabilities. Thanks to [@crawler-django](https://github.com/react-component/table/pull/619) for his contribution at that time, so we don't need to implement the flattening logic again. But in testing, we found a strange phenomenon. When the table is rendered for the first time or re-render, there will be a very large lag. When debugging, it comes from the `useFlattenRecords` hook. It's strange that test code itself does not use the expandable tree function. It was found that there were a lot of GC operations in `useFlattenRecords`. And these operations are caused by a piece of inconspicuous code: ```tsx // Fake code. Not used in real word function flatten(data: T[] = []) { let tmpList: T[] = []; for (let i = 0; i < data.length; i += 1) { const record = data[i]; tmpList = [...tmpList, record, ...flatten(record.children)]; } return tmpList; } ``` When traversing, although `children` is empty and only enters recursion once. But when looping through each Record, a temporary empty array will be created. But when `dataSource` data is huge, they will continue to trigger GC to clean up these temporary arrays. So we added logic to avoid unnecessary consumption: ```tsx // Fake code. Not used in real word function flatten(data: T[] = [], list: T[] = []) { for (let i = 0; i < data.length; i += 1) { const record = data[i]; list.push(record); flatten(record.children, list); } return list; } ``` ### RowSpan & ColSpan If you are familiar with the implementation of Table, you will know that row and column merging is achieved through `rowSpan` and `colSpan`. In virtual scrolling, since not all nodes are rendered, there will be cases where the rows and columns to be rendered do not exist: RowSpan To render this content, we need to calculate the `rowSpan` and `colSpan` of all Records in the current visible area. And this calculation process is very complicated. We need to traverse all Records and calculate the `rowSpan` and `colSpan` of each Record. Obviously, this is a very time-consuming operation, and when the `rowSpan` data is too far away from the visible area, the amount of content it needs to render will also be very large: Huge Size Maybe you will think of whether we can calculate the `rowSpan` in advance and then get these data when scrolling. This is actually not possible. The row and column data is provided by `onCell`, and calculating `onCell` every time when rendering the parent node will cause huge performance loss: ```jsx const Demo = () => { const [spanCount, setSpanCount] = useState(3); const columns = [ { dataIndex: 'group', onCell: (_, index) => ({ rowSpan: index % spanCount === 0 ? spanCount : 0, }), }, ]; // WOW! React.useEffect(() => { setSpanCount(5); }, []); return
    ; }; ``` Thus, even if we count the `rowSpan` data and render the rows outside the screen, it is still not enough. It may appear that `rowSpan` alternates: Multiple Row Span And for the worst case, all rows have `rowSpan` with other rows, then the amount of content we need to render will be the entire `dataSource`. That is, virtual scrolling is no longer virtual. Therefore, we need to clip it to render only the `rowSpan` in the visible area, and remove the irrelevant parts outside the screen: cut off So, think backwards. We only need to start from the visible area. Then get the Records affected by `rowSpan` up and down. Then only render the `cell` that provides `rowSpan`: fully cut off `rc-virtual-list` provides the `extraRender` method, which will provide the row number currently rendered in virtual scrolling. We only need to execute `onCell` on each Record in this range to get the `rowSpan` and `colSpan` information of each `cell`. So we can know whether the current row has `rowSpan`: ```tsx // Fake code. Not used in real word const extraRender = ({ start, end }) => { // Start record const startRecord = flattenData[start]; columns.forEach((col) => { // `rowSpan` === 0 means upper record has `rowSpan` const { rowSpan } = col.onCell(startRecord, start); }); // End record const endRecord = flattenData[end]; columns.forEach((col) => { // `rowSpan` > 1 means it should extend to next records const { rowSpan } = col.onCell(endRecord, end); }); }; ``` You should note that, in the actual collection process, we will record all `cell` with `rowSpan` in the range instead of just the head and tail Record. Then render these `cell` through the `extraRender` method (and skip rendering for `cell` affected by `rowSpan` in the original Record). This ensures the correctness of `rowSpan`. Of course, this implementation is based on the assumption that `rowSpan > 1` and `rowSpan = 0` will appear. It does not support the case where `rowSpan` is used to squeeze to the lower level, but for data tables, this is enough. ## Finally Virtual scrolling is a very complex feature, and there are many factors to consider. But we believe that it is worth spending this effort, and developers no longer need to choose between functionality and performance. Instead, you can have both. That's all. --- Title: 📢 v4 surpassed maintenance period URL: https://ant.design/docs/blog/v4-ood --- For our release schedule, the maintenance period for Ant Design v4 has officially ended at the end of 2023. This means that we will not release any new updates or patches for v4 unless significant defects or other serious issues are discovered. We strongly recommend that users upgrade to Ant Design v5 as soon as possible. You will get a series of benefits from upgrading to v5, including more powerful design system theme capabilities, richer component functionality, performance optimization, and more. In addition, v5 also includes many issue fixes and user experience improvements based on community feedback. We will continue to provide continuous support and updates on v5 to ensure that developers can get the best user experience. For a smooth transition to v5, we provide detailed upgrade guides and documentation. We understand that the upgrade process may involve a lot of work, so our team is also working hard to make this process as seamless and simple as possible. If you encounter any problems during the upgrade process, please feel free to submit an issue on GitHub. Please visit our official website or view the v5 upgrade documentation directly to start your upgrade journey and enjoy the latest Ant Design experience. - [v4 to v5](https://ant.design/docs/react/migration-v5) - [Less variables to Component Token](https://ant.design/docs/react/migrate-less-variables) - [CSS Compatible](https://ant.design/docs/react/compatible-style) --- Title: Type Util URL: https://ant.design/docs/blog/type-util --- The definition of TypeScript is very powerful, it can solve many problems, help developers find type errors in advance to avoid painful debugging at runtime. In antd, we also export the basic definitions of components: ```tsx import React from 'react'; import { Table, type TableColumnsType } from 'antd'; const columns: TableColumnsType = [ { title: 'Name', dataIndex: 'name', key: 'name', }, ]; export default () =>
    ; ``` These definitions meet most scenarios, but sometimes developers want to get more refined type definitions, which antd may not export. In the past, we recommended developers to extend them by themselves through TypeScript's type gymnastics to meet their needs: ```tsx import type { SelectProps } from 'antd'; type SelectOption = NonNullable['options']>[number]; ``` It's not a difficult task for developer who are familiar with TypeScript. But for TypeScript beginners, this may be a difficult problem. Therefore, we have launched a type tool library to help developers simplify the process of extracting types. ### Type Util We now provide 3 additional utility types in antd: - `GetProps` - `GetProp` - `GetRef` Previous two are used to help developers extract the props type of the component, and the last one is used to extract the ref type of the component. We can understand the usage of these types through the following examples: #### Get props definition by GetProps Some sub-component definition may not be exported in antd. You can get it directly through `GetProps`: ```tsx import type { Checkbox, GetProps } from 'antd'; type CheckboxGroupType = GetProps; ``` #### Get property type by GetProp For the property type of the component, we can get it through `GetProp`. It has been encapsulated with `NonNullable`. So there is no need to consider the null case: ```tsx import type { GetProp, Select, SelectProps } from 'antd'; // Both of this can work type SelectOptionType1 = GetProp[number]; type SelectOptionType2 = GetProp[number]; ``` #### Get ref definition by GetRef Through `GetRef`, you don't need to remember what the ref type of the component is, HTMLElement or some special definition. Just use it: ```tsx import React, { forwardRef } from 'react'; import type { GetRef, Select } from 'antd'; type SelectRefType = GetRef; // BaseSelectRef const Div = forwardRef((_, ref) =>
    ); type DomRefType = GetRef; // HTMLDivElement ``` ### The End Here is the type util we provided, hope it can help you. If you have better ideas, please feel free to raise an issue or PR on GitHub. --- Title: Bundle Size Optimization URL: https://ant.design/docs/blog/tree-shaking --- In modern JS applications, unused module can be automatically removed by modular packaging tools. This process is called [Tree Shaking](https://developer.mozilla.org/en-US/docs/Glossary/Tree_shaking). However, if you are already very familiar with it, you will find that it is not so perfect in reality. We still need some extra operations to achieve the best size optimization effect. Today, let's talk about a problem that ConfigProvider causes Tree Shaking to fail. ### ConfigProvider and rc-field-form In daily maintenance, we encountered some problems that using ConfigProvider would cause bundle size to increase: - https://github.com/ant-design/ant-design/issues/41607 - https://github.com/ant-design/ant-design/issues/43019 - https://github.com/ant-design/ant-design/issues/42499 The community also found the package that was incorrectly packaged while giving feedback `rc-field-form`. Here we directly borrow the illustration in the issue: bundle size ConfigProvider provides global configuration capabilities, which also includes the custom template configuration of Form component verification information: ```tsx ``` Customize Since this feature dependents with the verification of the form, it is implemented by the FormProvider provided by the underlying `rc-field-form`. In antd, it will be aggregated with its own localized `validateMessages`: ```tsx // Sample only. Not real world code. import { FormProvider } from 'rc-field-form'; const ConfigProvider = ({ validateMessages, children }) => { const mergedValidateMessages = React.useMemo( () => merge(antdDefaultValidateMessages, validateMessages), [validateMessages], ); return ( {children} ); }; ``` Meanwhile, FormProvider itself encapsulates the FormContext of `rc-field-form`, which causes more content of `rc-field-form` to be packaged after introducing FormProvider: Deps You may think, can we optimize it? If `validateMessages` is not configured, we will not call this FormProvider? ```tsx // Sample only. Not real world code. import { FormProvider } from 'rc-field-form'; const ConfigProvider = ({ validateMessages, children }) => { let node = children; if (validateMessages) { node = {node}; } return node; }; ``` Unfortunately, this is not possible. Tree Shaking is a static compilation process, and `validateMessages` is a runtime configuration. So in the packaging process, we cannot know whether `validateMessages` exists, so we cannot achieve this optimization. ### Decompose Dependencies We can adjust `rc-field-form` dependencies, so that FormProvider can be decoupled. But obviously, we should not rely on the adjustment of third-party libraries though `rc-field-form` is also maintained by us. We should solve this problem fundamentally, so that ConfigProvider no longer depends on FormProvider. The implementation is also very simple. Since this is unique to `rc-field-form`, we directly extract a Context, so that ConfigProvider no longer perceives FormProvider: ```tsx // Sample only. Not real world code. import { ValidateMessageContext } from '../form/context.ts'; const ConfigProvider = ({ validateMessages, children }) => { const mergedValidateMessages = ... return ( // Just use the proxy context {children} ); }; ``` Form also consumes the proxy Context: ```tsx // Sample only. Not real world code. import Form, { FormProvider } from 'rc-field-form'; import { ValidateMessageContext } from './context'; export default (props) => { const validateMessages = React.useContext(ValidateMessageContext); return (
    ); }; ``` Decomposing the dependencies in this way: New Deps ### Final Tree Shaking provides an automated way to optimize bundle size, but we need to pay attention to some details. Otherwise, some dependencies may be incorrectly introduced. Thanks. --- Title: Tooltip align update URL: https://ant.design/docs/blog/tooltip-align --- In the `5.3.0` version, we will update the underlying dependency `@rc-component/trigger` of the Tooltip component to better implement adaptive alignment logic. Before that, let's talk about some problems encountered in the previous version. ### About Scroll Tooltip is append to `body` by default, and it will scroll along with it when scrolling in full screen. But when the target element of the Tooltip is placed in the scrolling container, it will not follow the scrolling because the scrolling container is different: [](https://codesandbox.io/s/ji-ben-antd-5-2-0-forked-mo31wr?file=/demo.tsx) We suggest to use `getPopupContainer` in FAQ, allowing developers to insert the popup element into the parent container of the target element through this method. But this solution is not perfect, because it requires the developer to determine which of the parent containers of the target element is the scrolling container. In a reused component, the component that uses the Tooltip may not be the same as the component it scrolls, which makes it not easy to set the target scroll container. ### About Margining Tooltip supports edge display within the scrolling range. But because the pop-up layer is a whole, the centered arrow cannot point to the target position after offset: [](https://codesandbox.io/s/ji-ben-antd-5-2-0-forked-z6frnr?file=/demo.tsx) We recommend using the `placement` property and configure `topLeft` to align the popup layer to the left to solve this problem before: Similarly, if it is a reused component. Maybe it doesn't always need to be displayed side-by-side, it will be very strange when the popup layer is indeed left/right aligned when an element is displayed in the middle. ### About Scale Tooltip uses the `dom-align` library for align, which will directly add `left` | `top` | `transform` styles to the dom node to achieve alignment, so in order to make it support the React life cycle, we encapsulated it on top of it `rc-align` component. In addition, it only cares about the alignment implementation, not the trigger timing itself. So the `rc-align` component will additionally add a ResizeObserver to monitor size changes, and then call `dom-align` for alignment. `dom-align` calculates the respective coordinate positions of the target element and the pop-up layer by traversing the parent layer nodes, and then calculates the difference according to the alignment rules. When the parent layer node has a `transform` style, it will cause the calculated coordinate position to be inaccurate, resulting in incorrect alignment: [](https://codesandbox.io/s/ji-ben-antd-5-2-0-forked-znqgc6?file=/demo.tsx) ## New Align Way The above problems such as scrolling and margining can be avoided in some ways, but the scaling problem cannot be solved. We hope that these problems can be solved by antd, rather than by the developers themselves. To this end, we rewrote the `@rc-component/trigger` component to integrate alignment logic and arrow logic. No longer depend on `rc-align` and `dom-align`. At the same time, use the new calculation method to avoid calculation problems caused by the `transform` style. ### Position Calculation Considering that there are various `position`s in the parent node of the popup element, it is not cost-effective to recursively search the parent element node to calculate the relative position. We only need to calculate the offset according to the final positions of the two, and then apply the final zoom ratio of the popup layer: 1. Generate the Popup element 2. Add the Popup style `left: 0` & `top: 0` to force it to be aligned to the upper left corner - There may be `fixed`, `relative`, and `absolute` nodes in `position` in the parent container of the Popup element, which does not affect our calculation of offset. Just make sure to make an offset at the `0/0` position 3. Obtain the position information of the target element and Popup element through `getBoundingClientRect` 4. Calculate the offset difference Popup Align ### Scale The zoom ratio cannot be obtained directly, but we can calculate the zoom ratio through `getBoundingClientRect` and `offsetWidth`/`offsetHeight`: ```tsx const popupRect = popupEle.getBoundingClientRect(); const { offsetWidth, offsetHeight } = popupEle; const scaleX = popupRect.width / offsetWidth; const scaleY = popupRect.height / offsetHeight; ``` Then apply the scaling to the calculated offset: ```tsx // Some logic for align offset calculation // const baseOffsetX = ... // const baseOffsetY = ... const scaledOffsetX = baseOffsetX / scaleX; const scaledOffsetY = baseOffsetY / scaleY; ``` ### Arrow In the past, arrows were added by `@rc-component/tooltip` instead of `@rc-component/trigger`. This makes the `@rc-component/tooltip` lost the alignment information, so that the arrow position cannot be adjusted correctly when the Popup is offset. To this end, we also integrate the arrow logic into `@rc-component/trigger`, so that the position of the arrow can be offset with the offset of the Popup. After merging, the arrow position calculation becomes very simple. We only need to take the minimum value of the target element and the Popup boundary value, and then take the middle value: #### Center Position center #### Margining Position center ### Visible Region The new monitoring mode will detect the `overflow` style of the Popup parent node when the Tooltip is started. When `scroll`, `hidden`, and `auto` exist, the visible area except the scroll bar will be superimposed to calculate the final display area: VisibleRegion Similarly, we need to listen to its scrolling events. When any parent node is scrolled, the display area needs to be recalculated: ```tsx function collectScroll(ele: HTMLElement) { const scrollList: HTMLElement[] = []; let current = ele?.parentElement; while (current) { if (isScrollContainer(current)) { scrollList.push(ele); } current = current.parentElement; } return scrollList; } const targetScrollList = collectScroll(targetEle); const popupScrollList = collectScroll(popupEle); // We merge the list in real world. Here just for sample [window, ...targetScrollList, ...popupScrollList].forEach((ele) => { ele.addEventListener(...); }); ``` In the end, we get the effect of adaptive scrolling: scroll ## Finally After completing the transformation of Tooltip, we will continue to transform other components which has popup element. We hope that after this, developers can use components directly instead of paying attention to the configuration of `getPopupContainer` as much as possible. Have a nice day! --- Title: To be what you see URL: https://ant.design/docs/blog/to-be-what-you-see --- With daily development, have you thought about a problem. When the range limit is different from the actual value, how should we deal with it? Suppose we have a display component that simply displays your value: ```tsx interface StrProps { value: string; } function MyStr({ value }: StrProps) { return
    {value}
    ; } ; ``` Without a doubt, `Hello World` should be displayed on the page. Next, we add a scope limit: ```tsx interface StrProps { value: string; maxLen?: number; } ``` What should be displayed if we use a value out of range at this time? ```tsx ``` "Obviously", since you have `maxLen`, you should display `Hello` instead of `Hello World`. But this intuitive approach is not correct in all cases. If you use native input, you will find that the behavior is not like this: ```tsx ``` input limit As described by the standard, `maxLength` only limits user input. Is this standard wrong? > A form control maxlength attribute, controlled by the dirty value flag, declares a limit on the number of characters a user can input. ### "Unnecessary over design" With the above questions in mind, we imagine an input scenario. Now you have an e-commerce system, set prices for products: ```tsx ``` Form One day your manager said that the price of our product cannot exceed $99 according to regulations, and you have to set the limit directly on the form. This change is not difficult: ```diff -- ++ ``` But for existing products, we obviously cannot restrict them directly on the form. Otherwise, when the user edits the product, he will find that the price of his product has been changed. This is obviously unreasonable. Form modify (Users will never be able to understand why the data in the background does not match what they see) In fact, in many scenarios, components should not directly modify the actual value. Especially for input components, changing the display value without authorization will have very serious consequences. ### To be what you see At the component library level, we cannot "guess" the user's usage scenarios, so we need to implement the processing of boundary scenarios in the most conservative way. But at the same time, we can actually do some optimization methods. For example, set the restriction to the `rules` of Form.Item, and use the form validation ability to make restrictions: Form rules For some components themselves, it is also possible to add explicit style reminders: InputNumber For non-input custom components, you can also consider reminding users through design. For example, we can add a Tooltip to the display component: ```tsx // Same demo we've seen before ``` Customize Or use some other display way: Ellipsis ### Finally Boundary scenarios need to be carefully handled when developing components. In complex system, upstream users may not know how your internal logic is handled. Therefore, as the complexity and usage scenarios increase, we recommend always choosing a conservative approach to the default behavior. For situations that do not meet the requirements, it can be implemented in the form of HOC or some additional Props configuration, so as to prevent developers from having too many agreements when using it without knowing it. --- Title: How to Grow as a Collaborator URL: https://ant.design/docs/blog/to-be-collaborator --- Hello everyone, I am [heiyu](https://github.com/heiyu4585). About Ant Design, I believe everyone is very familiar with it. Before I contributed to Ant Design, I have used Ant Design in many background management system projects at work. The biggest feeling for me is that it is easy to use, beautiful, simple and stable. Now that the v5 version has been released, I strongly recommend everyone to try it. I am also fortunate to have developed the v5 version of the `Tour` component and `App` component, as well as some other maintenance work. Let me share with you the PR process of Ant Design, hoping to provide a reference for who are interested in building together for the community. ### Read related articles to familiarize yourself with related concepts [Contributing](https://ant.design/docs/react/contributing) [How to gracefully contribute code on github](https://segmentfault.com/a/1190000000736629) [Become a Community Collaborator](https://github.com/ant-design/ant-design/wiki/Collaborators#how-to-apply-for-being-a-collaborator) [developer notes](https://github.com/ant-design/ant-design/wiki/Development) [Some tips about git with PR](https://github.com/ant-design/ant-design/discussions/37051) ## Pull Ant Design code to local ### 1. Fork project - First you need to fork the project, enter the [project page](https://github.com/ant-design/ant-design), click the [Fork button](https://github.com/ant-design/ant-design/fork) - Ant Design link will appear in your github account is https://github.com/heiyu4585/ant-design this project - Use the following command on the project address on the local computer: get a github folder ```bash git clone https://github.com/[yourGithubAccount]/ant-design.git ``` Note: `[yourGithubAccount]` changed to your own github username ### 2. Add remote branch address - Go to the Ant Design folder and add the remote address of Ant Design ``` cd ant-design git remote add upstream https://github.com/ant-design/ant-design ``` - Pull the latest remote branch version ```bash git pull upstream master ``` Now we are on the master branch from the fork, and this master is reserved for remote code tracking upstream ### 3. Create a new fix branch on github ![image-20221211130607684](https://user-images.githubusercontent.com/10607168/208016775-623abfe7-fa7f-438d-abc3-be445e52d8c5.png) ### 4. Pull the new branch locally ```bash git pull git checkout fix-branch ``` Now we can change the code on the branch ## Find the issue on the [Ant Design issue](https://github.com/ant-design/ant-design/issues) page and analyze the selection To help you start your first attempt, we use [good first issues](https://github.com/ant-design/ant-design/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue") marks bugs and small features that are relatively easy to fix, and these issues are good as your first try. [help wanted](https://github.com/ant-design/ant-design/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) After all, it is easy to take over as a developer some problems. ![image-20221216111126983](https://user-images.githubusercontent.com/10607168/208016864-fd72d378-a5db-4c20-9a34-b136d5e7c446.png) ## Development Process 1. `npm start` A website running Ant Design locally 2. As issue mentioned. Debug, fixing or add new feature ## Run test cases and specification checks 1. When add new related test case, also make sure all tests pass `npm run test`. Tips: You can use `npm test -- --watch TestName` to run specified tests during development. 2. Run `npm test -- -u` to update [jest snapshot](https://facebook.github.io/jest/docs/en/snapshot-testing.html#snapshot-testing-with-jest) and put These updates are also committed (if any). 3. Make sure your code passes the lint check `npm run lint`. ## Merge changes - A common problem is that the remote upstream (ant-design/master) has a new update, which will lead to conflicts when we submit the Pull Request, so we can put the commits of other remote developers and our commit is merged. - Switch to the `master` branch with the following code: ```bash git checkout master ``` - Use the following code to pull the latest code from the remote: ```bash git pull upstream master ``` - switch back to fix-branch ```bash git checkout fix-branch ``` - Merge the `commit` of `master` into `fix-branch`, and resolve conflicts if there are conflicts: ```bash git rebase master ``` - Submit the updated code to your own `fix-branch`: ```bash git push origin fix-branch ``` ## Submit a Pull Request You can switch to the branches page on your github code repository page, click the fix-branch branch, click the `New pull request` button, add relevant comments and submit. Or switch to the code repository of the fix-branch branch, click the `Compare & pull request` button, add relevant comments and submit. - On the [PR page](https://github.com/ant-design/ant-design/pulls), carefully fill in the submission description according to the default format, and you can refer to the merged PR. - Check whether all the checks are passed. If you don’t click `details`, check the corresponding error report, and push again after repairing. ![image-20221210233540659](https://user-images.githubusercontent.com/10607168/208016178-5edb30af-7191-4ca0-a2d1-17c833f9ed92.png) ## Accept the maintainer's review and modify it, and wait for the maintainer to merge after passing the test ![image-20221216104628528](https://user-images.githubusercontent.com/10607168/208016926-f8ec6cf3-a599-481f-9611-d894975ab5f5.png) ## Common errors - PR description is not filled in as required ![image-20221210234139748](https://user-images.githubusercontent.com/10607168/208016993-7b1b6838-5944-4098-85ed-d0ea4567f42f.png) - Not rebase to latest version ![image-20221210234002553](https://user-images.githubusercontent.com/10607168/208017056-9a209552-29f3-48ab-ad09-90fde458147c.png) - react 16 test failed ![image-20221212091630186](https://user-images.githubusercontent.com/10607168/208017142-c9ee4169-f2d0-4085-bcff-6c859ec54e71.png) Repair method: ```bash npm run install-react-16 npm run test component/XXX ``` ## To be collaborator After a period of continuous maintenance, Collaborators will start the invitation mechanism and initiate a vote in [#3222](https://github.com/ant-design/ant-design/issues/3222). When enough votes are met, you will be officially invited to become a Collaborator. ![Collaborators](https://user-images.githubusercontent.com/5378891/209089697-4fe3f3b3-ef44-4d63-94c2-d93d082c9951.png) ## Don't be afraid to make mistakes, do it bravely, everyone is welcome in the open source world. ![giphy](https://user-images.githubusercontent.com/10607168/208015974-04c3f09b-b5e8-4ef7-af00-0bb5652ec619.gif) ## Related resources To learn more about Ant Design's development process and considerations, see: - [contributor development maintenance guide](/docs/blog/contributor-development-maintenance-guide) --- Title: about antd test library migration URL: https://ant.design/docs/blog/testing-migrate --- Hello, I am **[@li-jia-nan](https://github.com/li-jia-nan)**. It is also a new Collaborator who joined antd in the past few months. Fortunately, as one of the Collaborators, I developed the **[FloatButton component](/components/float-button)** and **[QRCode component](/components/qrcode)**, as well as some other maintenance work. Let me share the migration of the antd test library son~ ## introduction In `antd@4.x`, **[enzyme](https://enzymejs.github.io/enzyme)** is used as the test framework. However, due to the lack of maintenance of enzyme, it is difficult to support it in the React 18 era . Therefore, I had to start a long **[@testing-lib](https://testing-library.com/docs/react-testing-library/intro)** migration road for antd. During the migration process, I undertook about a quarter of the workload of antd. Here I mainly record the problems encountered during the migration process. > Thanks for the time [@zombieJ](https://github.com/zombieJ) [@MadCcc](https://github.com/MadCcc) [@miracles1919](https://github.com/miracles1919) for help. ![image](https://user-images.githubusercontent.com/49217418/207530591-1faaf171-638b-40af-8d61-3f07cb60abe2.png) ![image](https://user-images.githubusercontent.com/49217418/207530491-4988ecc4-2da0-4a0c-ba5d-b9797edecd1a.png) ![image](https://user-images.githubusercontent.com/49217418/207530507-412f0244-3d88-4500-9eb4-054f3e112731.png) ## start Before migrating, we need to figure out what the purpose of the migration is. In `enzyme`, most scenarios are to test whether the state in the component is correct, or whether the static properties on the class are assigned normally, which is actually unreasonable, because we need to care more about whether the "function" is normal , rather than whether the "attribute" is correct, because the source code is a black box for the user, and the user only cares about whether the component is correct. Basically, test cases should be written based on "behavior", not "implementation" (this is also the goal of `testing-library`). In principle, several use cases were found to be redundant (because some functions would not be triggered individually in real code), and their removal did not affect the test coverage. Of course, this is only one of the reasons to drop `enzyme`. More importantly it is unmaintained and does not support React 18 anymore. ## migrate ### 1. render `enzyme` supports rendering in three ways: - shallow: Shallow rendering, which is an encapsulation of the official Shallow Renderer. Render the component into a virtual DOM object. The component obtained through Shallow Render will not have a part asserted to the sub-component, and the information of the component can be accessed using jQuery. - render: Static rendering, which renders the React component into a static HTML string, then parses the string, and returns an instance object, which can be used to analyze the html structure of the component. - mount: Fully rendered, it loads component rendering into a real DOM node to test the interaction of DOM API and the life cycle of components, and uses jsdom to simulate the browser environment. In order to be close to the real scene of the browser, `antd@4.x` uses `mount` for rendering, and the corresponding `render` method in `@testing-library`: ```diff -- import { mount } from 'enzyme'; ++ import { render } from '@testing-library/react'; -- const wrapper = mount( ++ const { container } = render( , ); ``` ### 2. interact & event `enzyme` provides `simulate(event)` method to simulate event triggering and user interaction, `event` is the name of the event, and the corresponding `fireEvent` method in `@testing-library`: ```diff ++ import { fireEvent } from '@testing-library/react'; -- wrapper.find('.ant-handle').simulate('click'); ++ fireEvent.click(container.querySelector('.ant-handle')); ``` ### 3. DOM element In `enzyme`, some built-in APIs are provided to manipulate dom, or find components: - instance(): Returns an instance of the test component - at(index): returns a rendered object - text(): Returns the text content of the current component - html(): Returns the HTML code form of the current component - props(): Returns all properties of the component - prop(key): Returns the specified property of the component - state(): Returns the state of the component - setState(nextState): Set the state of the component - setProps(nextProps): Set the properties of the component - find(selector): Find the node according to the selector, the selector can be the selector in CSS, or the constructor of the component, and the displayName of the component, etc. In `testing-library`, these APIs are not provided (as mentioned above - `testing-library` focuses more on behavioral testing), so it needs to be replaced by native dom operations: ```diff expect(ref.current.getPopupDomNode()).toBe(null); -- popover.find('span').simulate('click'); -- expect(popover.find('Trigger PopupInner').props().visible).toBeTruthy(); ++ expect(container.querySelector('.ant-popover-inner-content')).toBeFalsy(); ++ fireEvent.click(popover.container.querySelector('span')); ++ expect(container.querySelector('.ant-popover-inner-content')).toBeTruthy(); ``` ### 4. compatibility test While the major version is being upgraded, some components are discarded, but they are not removed in antd. For example, the BackTop component needs to add warning to the component to ensure compatibility, so it is also necessary to write a special unit test for warning: ```diff describe('BackTop', () => { ++ it('should console Error', () => { ++ const errSpy = jest.spyOn(console, 'error').mockImplementation(() => {}); ++ render(); ++ expect(errSpy).toHaveBeenCalledWith( ++ 'Warning: [antd: BackTop] `BackTop` is deprecated. Please use `FloatButton.BackTop` instead.', ++ ); ++ errSpy.mockRestore(); ++ }); }); ``` ## Diff Mystery During the conversion process, I discovered a magical phenomenon. In some cases, the DOM snapshot generated by the same case will be different, so I began to explore what has changed in React 18: In the past, the `snapshot` comparison of `enzyme` was to convert the `enzyme object` into a serialized object through the `enzyme-to-json` plugin: ```js // jest.config.js module.exports = { // ... snapshotSerializers: ['enzyme-to-json/serializer'], }; ``` When it comes to `@testing-library/react`, directly call `render` to generate dom elements, and then compare the dom: ```diff -- import { mount } from 'enzyme'; ++ import { render } from '@testing-library/react'; describe('xxx', () => { it('yyy', () => { -- const wrapper = mount(); ++ const { container } = render(); -- expect(wrapper.render()).toMatchSnapshot(); ++ expect(container.firstChild).toMatchSnapshot(); }); }); ``` Interestingly, in some test cases. It will hang, the difference is that React 18 sometimes has fewer blank lines: ```diff
    -- Hello World
    ``` After testing `innerHTML` of dom, it is found that 17 and 18 are the same. So at the beginning of the problem, we simply changed the test case to compare `innerHTML`: ```ts expect(container.querySelector('.className').innerHTML).toMatchSnapshot(); ``` However, as you migrate more, you will gradually see this happening over and over again. Comparing `innerHTML` is also not a long-term solution. So began to explore why this happens. ## pretty-format `pretty-format` is an interesting library that converts any object into a string. One of its uses is for snapshot comparison of jest. One of its features is that conversion rules can be customized. Compared with `snapshot` in `jest`, `format` will be done first, for common objects such as native `dom`, `object`. It has built-in a set of `plugins` for format conversion: ```html
    Hello

    World

    ↓
    Hello

    World

    ``` The first reaction to the appearance of extra spaces is whether it is because the version of `@testing-lib/react` introduced by 17 & 18 is different, which affects the version of `pretty-format` that `jest` depends on. After checking, they are all consistent: ```json { "devDependencies": { "pretty-format": "^29.0.0", "@testing-library/react": "^13.0.0" } } ``` After this judgment is wrong, it is another situation. There is an `empty element` in the dom, which makes `pretty-format` perceptible, but it does not affect `innerHTML`, so I wrote a simple test case: ```ts const holder = document.createElement('div'); holder.append(''); holder.append(document.createElement('a')); expect(holder).toMatchSnapshot(); console.log(holder.innerHTML); ``` and get the following output: ```snap // snapshot exports[`debug exports modules correctly 1`] = ` `; // console.log ``` Consistent with the idea, then it is very simple. Then there is a high probability that the `render` of `React 18` will ignore empty elements. Let's do a simple experiment: ```tsx import React, { useEffect, useRef, version } from 'react'; const App: React.FC = () => { const holderRef = useRef(null); useEffect(() => { console.log(holderRef.current?.childNodes); }, []); return (

    {version}

    ); }; export default App; ``` as predicted: | React 17 | React 18 | | ----------------------- | -------------- | | NodeList(2) \[text, p\] | NodeList \[p\] | Check the `Fiber` node information, you can find that `React 17` will treat empty elements as `Fiber` nodes, while `React 18` will ignore empty elements: > React 17: ![image](https://user-images.githubusercontent.com/49217418/207533725-fb8f9e4d-7f09-4a13-a04a-cbb2d3eb2aea.png) > React 18: ![image](https://user-images.githubusercontent.com/49217418/207533740-328d10ea-d9bc-4469-bc00-f08e33857e6f.png) You can find the relevant PR by following the map: - https://github.com/facebook/react/pull/22807 ![WX20230319-145539@2x](https://user-images.githubusercontent.com/49217418/226159376-497fd490-153e-4e88-92e2-29dda50b3426.png) ## a solution Antd needs to test React16, 17, and 18. If snapshot is not feasible, it will cause too much cost. So we need to modify jest. `enzyme-to-json` gave me inspiration, we can modify the snapshot generation logic to smooth out the diff between different versions of React: ```ts expect.addSnapshotSerializer({ // Determine whether it is a dom element, if yes, go to our own serialization logic // The code has been simplified, more logic is needed for real judgment, you can refer to setupAfterEnv.ts of antd test: (element) => element instanceof HTMLElement, // ... }); ``` Then access `pretty-format` and add your own logic: ```ts const htmlContent = format(element, { plugins: [plugins.DOMCollection, plugins.DOMElement], }); expect.addSnapshotSerializer({ test: '//...', print: (element) => { const filtered = htmlContent .split(/[\n\r]+/) .filter((line) => line.trim()) .map((line) => line.replace(/\s+$/, '')) .join('\n'); return filtered; }, }); ``` ## knock off The above are some problems encountered during the migration of the antd test framework. I hope to help students who need to migrate or have not yet started writing test cases. Everyone is also welcome to join the antd community and contribute to open source together. --- Title: Suspense breaks styles URL: https://ant.design/docs/blog/suspense --- We know that React 18 provides a `useInsertionEffect` hooks specifically for CSS-IN-JS, which has a faster timing priority than `useLayoutEffect`, so that the order of calls will not be affected by the order of writing: ```tsx useLayoutEffect(() => { console.log('layout effect'); }, []); useInsertionEffect(() => { console.log('insertion effect'); }, []); // Console: // - insertion effect // - layout effect ``` In early `@ant-design/cssinjs` implementation, we did not choose `useInsertionEffect` because we needed to be compatible with React 17 version, but simulated the effect of inserting in advance by adding styles in the render phase: ```tsx // pseudocode. Not used in real world function useStyleInsertion(hash: string, counter: Record) { useMemo(() => { if (!counter[hash]) { // Insert only when current style not inserted } counter[hash] += 1; }, [hash]); useEffect( () => () => { counter[hash] -= 1; if (!counter[hash]) { // Remove if set to clear on destroy } }, [hash], ); } ``` Above code will count the usage of styles, if the current style has not been inserted, it will insert the style in the render phase. Similarly, if the current style is configured to be unloaded when it is not in use, it will be cleared after the effect confirms the count. In addition, there is a similar logic that listens for changes in tokens, and when there are multiple tokens, it will clear all styles `
    ``` This implementation is simple and effective, the only downside is style pollution for `:nth` selections. But considering that antd components rarely use this selector, the side effects can be ignored. It worked well at the beginning, and the official website of antd directly supports the SSR style without modification and meet the SEO needs. But as our components gradually migrated to the CSS-in-JS version, we found that the site's bundle size became very large and slowly became unusable. After looking at the HTML, we found that the default inline method is not good, it will cause the style to be doubled inline, for example, if there are 3 Buttons in a page, then it will repeat the inline 3 times: ```html
    ``` And when most components are converted to CSS-in-JS, inline styles can become huge. So we removed the automatic inlining function in the later stage, and converted it to a form that needs to be collected manually: ```tsx import { createCache, extractStyle, StyleProvider } from '@ant-design/cssinjs'; import { renderToString } from 'react-dom/server'; const cache = createCache(); // HTML Content const html = renderToString( , ); // Style Content const styleText = extractStyle(cache); ``` This is the traditional CSS-in-JS injection implementation. As mentioned in the introduction, inline styles cannot be cached and cause additional loading overhead. Therefore, we try to explore some new implementation methods to obtain a loading experience like native CSS. ### Static Extract Style We are thinking about whether we can pre-bake the style of the component for front-end consumption like the v4 version, so we proposed [\[RFC\] Static Extract style](https://github.com/ant-design/ant-design/discussions/40985). Its idea is very simple that only need to render all the components once in advance to get the complete style from the cache, and then write it into the css file. ```tsx const cache = createCache(); // HTML Content renderToString( ``` In the current theme system of Ant Design 5.0, the hash values corresponding to these two buttons are different. As a result, their styles do not affect each other, illustrating the role of hash in theme isolation. However, in the CSS variable solution, the modification of these two tokens does not actually affect the calculation of the hash. Consequently, theme isolation breaks down, and both `colorPrimary` values end up under the same hash, leading to mutual overlap. To maintain theme isolation, we require different hash values for Button 1 and Button 2, creating a clear contradiction and a new issue. Let's reconsider the original intention of adopting CSS variables: to achieve faster theme switching and reduce the performance overhead of theme changes. It can be observed that the emphasis is on **switching**. For nested or parallel themes, their focus is not on "switching" but on "isolation." Therefore, they require distinct and stable hash values, and in most scenarios, their HTML remains stable. For theme switching, the emphasis is on "switching". What we expect is to achieve fast and high-performance theme switching using CSS variables under a fixed hash (i.e., stable HTML). This does not conflict with theme isolation. Therefore, we still need different hashes to achieve CSS variable isolation. On top of this, different themes corresponding to various hash values can be generated based on user preferences for CSS variable styles. It might sound a bit abstract, so let's use code to explain the desired outcome. Taking the example of nested themes mentioned earlier, here's what we want the generated CSS file to include: ```css :where(.css-hash1).ant-btn { background-color: var(--color-primary); } :where(.css-hash2).ant-btn { background-color: var(--color-primary); } .css-hash1 { --color-primary: blue; } .css-hash2 { --color-primary: green; } ``` The result is as expected, combining CSS variables with hashes. But in fact, we should adjust our thinking slightly and return the hash calculation to the original value of the token, or directly use CSS variables to calculate the hash: ![image](https://github.com/ant-design/ant-design/assets/27722486/e4c2a109-34d6-4fe7-a3e4-03ed532775b8) ### CSS Variables Switching So far, we have integrated theme isolation with CSS variables using hash, meeting our ambitious goals. However, there is still an issue with hash. It is dynamically calculated, and users cannot know the hash value in advance, making it impossible to directly manipulate CSS variables using JavaScript. But there is always a solution. Besides directly using JavaScript to modify CSS variables, we can also utilize CSS selectors to switch CSS variables in different scenarios. This requires us to generate CSS variables for different themes in advance: ```css /* Using custom classes as selectors */ .light .css-hash { --color-text: rgba(0, 0, 0, 0.85); } .dark .css-hash { --color-text: rgba(255, 255, 255, 0.88); } ``` At this point, we only need to switch the class on the outermost DOM element wrapping the component to easily achieve theme switching. This outer DOM element can be `html`, `body`, or a specific element in the application. It depends on users. The problems always seem to be interconnected. We mentioned that the hash is normally calculated based on tokens, but when it comes to dynamic switching, we want the hash to remain constant. So, for the two sets of themes mentioned earlier, their hashes should be consistent, even though their corresponding CSS variables are different. Therefore, we need to make some adjustments to the hash calculation method. ![image](https://github.com/ant-design/ant-design/assets/27722486/43639237-e286-4a06-85c2-f2e93d82087a) In fact, it can be observed that after applying CSS variables, what we have been doing is turning the 'dynamic' into 'static', making every effort to avoid dynamically modifying tokens using JavaScript. This is crucial as it would trigger JavaScript computation, thereby slowing down webpage performance. Conversely, we leverage the static compilation capability of CSS variables to gradually narrow down the scope of things that would change at runtime. Ultimately, it becomes a matter of efficiently switching themes by modifying only a class name or a DOM attribute. Finally, don't forget that tokens can be passed through the context. In the case of nested themes, the current tokens inherit values from the context to override them. As described earlier, we need to provide multiple tokens in the theme, each with a different theme name. If multiple themes are used in nested themes at different levels, the computational complexity is actually multiplied. For example: ![image](https://github.com/ant-design/ant-design/assets/27722486/c5493235-68af-495c-b5cd-7e1730c38898) This can become a potential burden. ### Dynamic Themes with CSS Variables Consider the following scenario: users can freely modify the theme color and text font size on the webpage to suit their preferences. This scenario does not align with the research discussed earlier because our previous study was based on a complete set of known themes (such as a dark theme). When users can freely modify the value of a variable, we cannot pre-build the theme; instead, we must rely on runtime capabilities for modifications. This situation can be referred to as a true 'dynamic theme'. As mentioned earlier, there are two obstacles to implementing dynamic themes based on CSS variables: 1. Changes in hash values will cause components and the DOM to re-render. 2. Users cannot know the hash value in advance. There are two solutions for these two points, respectively. #### Random Hash For the first issue, the apparent problem to solve is the dynamic hash value caused by token changes. The existence of hash values serves two purposes: style isolation and caching. In the context of dynamic CSS themes, we can discard the caching feature since we have replaced all tokens with CSS variables. The styles themselves do not change; each token change only affects the inserted CSS variables. At this point, the performance impact of serializing CSS has been significantly reduced. Therefore, we can use random hashes to ensure style isolation. ![image](https://github.com/ant-design/ant-design/assets/27722486/c7128e5e-6330-4dd4-939f-312e11f88af3) At this point, we can see that users can simply modify tokens in the ConfigProvider, just like before, to use dynamic themes without any noticeable changes in usage. An additional point is that we eliminate the performance cost of calculating hashes here. However, as a trade-off, we might generate two sets of CSS variables that are identical, yet their hashes are different. The impact of this depends on the user's specific usage patterns. #### Custom Hash The above solution can actually address most of the issues in various scenarios. However, let's revisit a problem mentioned from the beginning: the FOUC issue. In a statically compiled web page, all theme changes implemented through React lifecycle methods cannot be reflected in the user's browser immediately. We must provide users with the ability to modify the theme before the browser renders the page. The implementation of this capability essentially involves allowing users to replace CSS variables in scripts. As mentioned earlier, one method is to directly replace the class or attribute on the HTML in the script to apply statically compiled CSS variables, which is not suitable for dynamic themes. Therefore, users need to directly modify the values of CSS variables in the script, introducing the problem of 'needing to know the hash value in advance.' If the hash value is completely random or calculated based on tokens, users cannot use this hash value outside the React lifecycle, or it is challenging to save this hash value for use in scripts outside the React lifecycle. In other words, as long as the user knows the hash value, is that sufficient? Therefore, we allow users to customize the hash value, and users do not need to worry about the loss of style isolation due to custom reasons—because we can easily detect if users are using the same hash value in the application. In this way, users only need to override hashed CSS variables in the format of Ant Design (antd)—we can provide a factory function to help users generate CSS variable styles. ![image](https://github.com/ant-design/ant-design/assets/27722486/257c5811-bd67-48b3-8ea3-29a428d96bc8) ### Farewell Hash After ceasing the active calculation of the hash, two questions arise: 1. Is it still a hash? 2. Do we still need to add hash to the styles? The first question is somewhat philosophical. From a historical perspective, it is still a hash. However, since it is no longer necessary to compute it, it is simply a pure random value or a user-defined string. The second question is crucial. Now that all tokens have been replaced, styles under different themes no longer have any differences, and the isolating role played by the hash is no longer significant. We still add the hash class to the DOM as the scope of the theme, which directly affects where the components derive their CSS variable values. However, the styles themselves do not care about these, so we can optimize further: ![image](https://github.com/ant-design/ant-design/assets/27722486/f49c5e57-f17e-4725-b850-43708e9a6235) Styles can now exist independently! This means that different themes can share the same set of styles—there is no longer a need to generate these styles repeatedly. However, we still need to consider micro-application scenarios. Although hash values are isolated between different versions of antd, styles lose their scope without a hash. Without hash, different versions of antd can contaminate each other. Therefore, we will still provide the ability to apply hash to the overall styles of the application—this is the application-level hash. Unlike the theme hash, the entire application can still reuse the same set of styles. --- Title: CSS in v6 URL: https://ant.design/docs/blog/css-tricks --- During the development of Ant Design v6, since there is no longer any need to consider IE compatibility, we modified some components to use CSS variables. This resulted in a smaller CSS footprint and better performance. Today, let's talk about some aspects of CSS variables. ## Variants In v5, some components supported the `variant` property to implement different styles, with the Button component being a typical example: ![Variant Button](https://mdn.alipayobjects.com/huamei_iwk9zp/afts/img/A*ApyYQpXQQfgAAAAAAAAAAAAADgCCAQ/original) (Combined with `color` to achieve different button combinations) In v5, the combination of Button variants and color would create a repetitive set of combinational styles: ```css /* Sample code. Not used in real world. */ .ant-btn-solid.ant-btn-red { color: #fff; background: red; } .ant-btn-solid.ant-btn-blue { color: #fff; background: blue; } .ant-btn-outlined.ant-btn-red { color: #fff; border: 1px solid red; } .ant-btn-outlined.ant-btn-blue { color: #fff; border: 1px solid blue; } /* ... */ ``` After converting to CSS variables, the logic shifts from directly defining styles to managing the color palette. Thus, after defining a basic set of colors, you can effortlessly generate styles via variables: ```css /* Sample code. Not used in real world. */ /* Template Part */ .ant-btn { color: var(--ant-btn-color); background: var(--ant-btn-background); border-color: var(--ant-btn-border-color); border-width: 1px; border-style: solid; } .ant-btn-solid { --ant-btn-color: #fff; --ant-btn-background: var(--ant-color-solid); } .ant-btn-outlined { --ant-btn-color: var(--ant-color-solid); --ant-btn-border-color: var(--ant-color-solid); } /* CSS Variables. The more color you have, the more size to save. */ .ant-btn-red { --ant-color-solid: red; } .ant-btn-blue { --ant-color-solid: blue; } /* ... */ ``` ## Style Overrides With CSS variables, overriding styles on the user side becomes much simpler. In the past, developers had to override styles for each state and consider specificity: ```css .ant-btn-solid.my-btn:not(:disabled) { background: #f00; } .ant-btn-solid.my-btn:not(:disabled):hover { background: #e00; } .ant-btn-solid.my-btn:not(:disabled):active { background: #d00; } .ant-btn-outlined.my-btn:not(:disabled) { color: #f00; border-color: #f00; } .ant-btn-outlined.my-btn:not(:disabled):hover { color: #e00; border-color: #e00; } .ant-btn-outlined.my-btn:not(:disabled):active { color: #d00; border-color: #d00; } ``` Overriding CSS variables, however, is much simpler: ```css .ant-btn-outlined.my-btn { --ant-color-solid: #f00; --ant-color-solid-hover: #e00; --ant-color-solid-active: #d00; } ``` ## Conditional Compatibility In v6, to achieve a more semantic structure, we adjusted the DOM of many components and also cleaned up the compatible Component Tokens provided during the v4 to v5 Less migration (more values are computed rather than manually configured by developers). However, to avoid affecting existing users, we aimed for maximum compatibility. One example is that when a certain token exists, we use an alternative style: ```less .sample { color: blue; } /* How to if? */ if (customVar exist) { .sample { color: red; } } ``` One idea was to add an extra `className` to the component based on the existence of the token: ```jsx const Sample = () => { const { token } = useToken(); // Sad. Component token is not exist in token. if (token.components.sample.customVar) { // ... } }; ``` Unfortunately, the component token is not available in `useToken`. It is only generated asynchronously during the component's rendering effect to avoid unnecessary performance overhead. Therefore, using conditional logic in CSS is a better option; here, we use `@container` to implement conditional logic: ```css /* Current container support css var `--custom-var` */ @container style(--custom-var) { /* ... */ } ``` Conditional Styles It is important to note that the CSS variable query in `@container` is not yet supported by Firefox. Therefore, in v6, we do not rely on `@container` as the primary functionality, but rather as a fallback compatibility mechanism. ## @scope If there is one of the most enticing properties in CSS, it would be `@scope`. In v5, we used `:where` to implement CSS namespaces, isolating styles for different versions or themes of antd components: ```css /* Theme 1 */ :where(.css-BamBoo).ant-btn { color: red; } /* Theme 2 */ :where(.css-LIghT).ant-btn { color: blue; } ``` However, this approach can sometimes cause issues with nested logic. For example, in the following case, styles for `span` under `Theme1` affect `Theme2`: ```css /* Theme 1 */ :where(.css-BamBoo) { .component-a span { color: red; } } /* Theme 2 */ :where(.css-LIghT) { .component-b { color: blue; } } ``` ```tsx
    Hello World
    ``` Whereas `@scope` can perfectly solve this problem: ```css @scope (.component-a) to (span) { /* ... */ } ``` Scope Impact However, similarly, `@scope` is not yet supported by Firefox. Applying it in v6 would result in Firefox users being unable to use antd components. Hence, you may only see it in the next major version. --- Title: Component-level CSS-in-JS URL: https://ant.design/docs/blog/css-in-js --- On November 18, 2022, we released Ant Design 5.0. At the same time, Ant Design's unique CSS-in-JS solution was brought into everyone's view. Through this solution, Ant Design achieves higher performance than other CSS-in-JS libraries, but at the cost of sacrificing its flexibility for free use in applications. So we call it a "component-level" CSS-in-JS solution. ## Dilemma of CSS-in-JS In CSS-in-JS, hash is used to confirm whether a style has been inserted. The way to calculate the hash is usually to convert a complete css into a hash value. For example, in emotion, we can see such a style tag by checking the elements on the page. The hash value corresponding to such a style tag is unique:
    ![image.png](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*X5tDQ5VIpcoAAAAAAAAAAAAADrJ8AQ/original)
    In this way, you can find a problem that CSS-in-JS has been criticized for a long time. What we write when coding is not the final css. So every time we need to serialize to get the css and calculate the hash again. If your page or component has a very complex or a large amount of CSS-in-JS code, and even the style will follow the component's props change, then this performance issue becomes non-negligible.
    To solve this problem, each CSS-in-JS library will have its own way to deal with it. Let’s take a look at Ant Design’s solution. ## Hash In fact, it is not difficult for us to find that the problem lies in the process of serializing css. How about reducing the times of serializing css by caching? For application-level CSS-in-JS, it is difficult for us to find a suitable key for cache. But if it is a component library, the final style is relatively stable.
    According to the style structure we determined from v4 and previous versions, the style of each component will not change under the same theme variable and the same version. Conversely, the style may change only if the theme variable is modified, or the version of antd is changed.
    From this we get a very simple way to calculate the hash:
    ![image.png](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*XuVYRJ_27Q0AAAAAAAAAAAAADrJ8AQ/original)
    We will apply the **same** **hash** to all antd components. In this way, when using the antd component, we only perform hash calculations on the current version and theme variables. Version can be obtained directly from `package.json`, and theme variables can be obtained directly from context. So we don't need to serialize css again and again to get a stable hash, and the performance is improved finally. ## Cache for Components In the above way, we have taken the first step of "component level" CSS-in-JS, but this is not enough. Since it is "component level", we can also optimize it again with components.
    In Ant Design, the style of a component is usually complete. That is to say, no matter what variant the component has, its style exist in the whole component style. In this way, we can draw a conclusion again: the props of antd components will not affect the component style.
    This is very important. In the application-level CSS-in-JS solution, since props may affect the component style, it is inevitable that the component style will be regenerated during the rendering phase. No matter how to optimize this point, it cannot be ignored. Now that we have adopted a "component-level" solution, this problem can be easily solved: do style caching for components.
    ![image.png](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*yZMNSYVtxnAAAAAAAAAAAAAADrJ8AQ/original)
    In the case of the same hash, no matter how many times the same component is used and rendered, the style will only be generated once at the first mount, and will hit the cache for the rest of the time. This is the second insurance for "component level" CSS-in-JS solutions. ## Benchmark At the release of Ant Design 5.0, we simply made a benchmark, and here are some supplementary instructions:
    ![image.png](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*upmYSqZ5FwsAAAAAAAAAAAAADrJ8AQ/original)
    The benchmark is based on generating a very long unchanging style to test the performance of basic usage of the three libraries. It can be seen that under the "component level" usage scenario of Ant Design, @ant-design/cssinjs has a performance advantage whether it is the first rendering or the second rendering. Since styled has certain optimizations when dealing with stable styles, the performance of secondary rendering in this benchmark is better, but it will still be affected by recalculation like emotion when props participate in style calculation. ## Limitation In the above comparison, it cannot be said that antd is definitely better than styled and emotion, but in the component-level usage scenarios, we have made corresponding optimizations to obtain performance advantages. Conversely, due to the limitation of "component level", antd's CSS-in-JS solution is not suitable for construction applications.
    Due to the special hash calculation method and component cache, when applying antd's CSS-in-JS solution, developers must provide stable hash and unique component names by themselves. For applications, automatic hash capabilities such as css modules are more needed. At the same time, caching a large number of components in the application also requires additional management costs. Once an error occurs, it is difficult to troubleshoot. Therefore, we recommend using the "component-level" CSS-in-JS solution in component libraries. --- Title: Contributor development maintenance guide URL: https://ant.design/docs/blog/contributor-development-maintenance-guide --- Hi, I'm [kiner-tang](https://github.com/kiner-tang) who is a heavy user of Ant Design. As the same reason, I come up to be a contributor for fixing bug and some features. Finally, it's my honer to become a member of Ant Design Collaborator. During the journey from user to contributor, and then from contributor to collaborator, I also encountered many problems. I would like to share my experience with the problem I meet. Hope it can help you to join the Ant Design community. ## Some frequently asked Questions ### About dependent version There are various of package managers, such as npm, yarn, or pnpm, providing version-locking solutions to avoid version-inconsistencies issue. However, in Ant Design projects, many functions depend on the original components in the `react-component` repository. We expect that when we encounter some bugs, after the `react-component` fixes and releases the patch version, Instead of manually upgrading the version in the Ant Design project, we can install the latest patch installation package only by reinstalling the dependencies. At this point, the version-lock file provided by the package manager is the main obstacle to automatic updates, because once the version-lock file is available, reinstalling the dependency will also install the version specified by the lock file and cannot be upgraded to the patch version. Based on the above reasons, we adopt the following methods: 1. Add `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml` and other version lock files to `.gitignore` without version tracking. 2. In `package.json`, for the dependencies that we want to update when there is a new patch version, we use `~` description version number to allow patch version update. ```json { "dependencies": { "@rc-component/cascader": "~3.9.0" } } ``` For the difference between `^` and `~` in the version description of package.json, see [What's the difference between tilde(~) and caret(^) in package.json](https://stackoverflow.com/questions/22343224/whats-the-difference-between-tilde-and-caret-in-package-json). Thus, when our dependency such as @rc-component/cascader fixes a bug and releases a patch version such as: `3.9.1`, then the user's latest installed version is `3.9.1`. For the maintainer of Ant Design, we only need to execute the following command: ```bash git clean -fdx npm i ``` ### Snapshot update problem In Ant Design, we use Jest for unit test. Many first-time contributors of Ant Design may be confused that CI failed after opening a pull request in which they just modify the text in a demo. This is caused by the snapshot diff test. In most libraries, idempotence is emphasized. With one method and same parameters, the result should be the same no matter how many times it is executed. In Ant Design, the main use of snapshot test is to verify the idempotence of demos, in order to ensure the stability and certainty of components. Actually, snapshot test is simple. By comparing HTML string generated by each demo in different runnings, we could get which one is broken in PR. Back to the topic, what should we do if we find snapshot test failed after changing a demo? 1. First, we need to check the snapshot diff to see whether it is the expected change. If there is only the text you modified in demo differs from the origin one, we just need to run the following command to update the snapshot: ```bash # Run the test command to update snapshot npm run test -u ``` 2. However, we should find what's going wrong if the diff of snapshot is not only caused by your modification this time. For example, you only modified the text, but found that classnames in snapshots have changed, which obviously does not meet expectations. The common causes are as follows: - Local dependency is out of date. This may happen when you pull the latest code, but did not update the local dependency. Deleting `lock` file, `node_modules`, and then reinstalling dependencies could solve this problem. solution is as simple as deleting the lock file, node_modules and reinstall dependencies. - Your code not synchronizing baseline code can also result in inconsistent snapshot comparisons. The solution is as simple as pulling the baseline code locally and then rebase your code to the baseline code. - You may have locally changed the source code not only in demos, which would cause unexpected change. You need to go through your change carefully. ### rc-x Library dependencies In Ant Design, most components are an upper encapsulation of a component based on `react-component`. Therefore, if we find a problem of `@rc-component/xxx` or `rc-xxx` component when troubleshooting, we need to open PR on those repositories to fix it. After coding, we need to verify that the problem in Ant Design is resolved, in which case we can link the project to Ant Design for verification. For example: Run `npm link` in the repo you are working on. ![image](https://user-images.githubusercontent.com/10286961/224603053-98488c2d-f33c-4c25-8c09-6c790cfcdbf6.png) Run `npm link "Project name"` in Ant Design ![image](https://user-images.githubusercontent.com/10286961/224603065-95715727-83d0-4ef9-81e4-3b7065aaf73e.png) Once we have verified, we can open PR to the repo. Noted that link may cause exceptions when running the test command. Therefore, we need to run the following commands locally to delete the package from link. ```bash npm unlink "@rc-component/form" --no-save npm i ``` When the PR is finally merged, usually the maintainers will release a version. If the patch version is released, you only need to install and verify it in Ant Design. But if the minor version is released, you need to upgrade it in Ant Design. After local verification, a separate PR to Ant Design could be opened for bugfix. ### Deprecation In a large project, if you want to remove a property or a method, it is actually very troublesome. Since your project may already have a lot of items in use, other projects depending on it may get broken. But as the project iterated, we will encounter more and more problems which solutions long time ago may no longer fit. Then, we need to adopt a soft, less radical way to remove it, leaving enough time for users to modify. In Ant Design, we adopt a **five-step strategic** to deprecate property or method: 1. **Add deprecated tag to the property** ![003](https://user-images.githubusercontent.com/10286961/224358324-8f72f2c0-d5bb-4281-9b29-7e2428353449.png) After adding the above deprecated tag, we can see warning when using this property: ![004](https://user-images.githubusercontent.com/10286961/224358351-958a168d-41de-44b0-8244-2f8d67c4d13a.png) 2. **Add console warnings** ![005](https://user-images.githubusercontent.com/10286961/224358371-09f08f79-8c95-4126-b382-59311bb702d6.png) It is important that after adding console warnings, we need to add a test case to test whether the warnings will be displayed when the deprecated properties are used. ![006](https://user-images.githubusercontent.com/10286961/224358407-3d89d2f5-b4aa-48b4-aab8-1331a0f620fa.png) 3. **Update document**: The above two steps are mainly to warn developers in the editor and browser. Next, we need to update the related document. Generally speaking, if we have a property deprecated, it means that it is not recommended for users to use. So we need to remove the related document and add the description of the new property in the meantime. If it cannot be deleted due to special circumstances, please specify the version this property is supported and the alternative scheme in the remarks column. 4. **Compatibility between old and new**: Now that we're done with the above tips, it's important to make sure that the new property and the deprecated one both works until the deprecated one is removed. That is to say, we must have the deprecated property work normally. We should not apply any changes in addition to the warning. ![007](https://user-images.githubusercontent.com/10286961/224358439-76c42c78-e244-42bd-8935-b08f536931a2.png) We can do something like this to make sure that the new property takes precedence over the old one. At this point, our property deprecation work is done. 5. **Remove**: After our properties have been deprecated for a certain period of time, usually when the major version is released, we can remove them. We also need to delete comments, warnings, test cases, and documents that were related to the property. At this point our property removal work is done. ## Take it to the next level After contributing for some time, we believe you have gained a deeper understanding of Ant Design's overall development process and project architecture. At this point, you may want to take on more tasks and contribute more to the open source community. Then, you can apply to be a Collaborator at Ant Design by commenting on the link below for more active contributors. [Add Collaborator permission for some active contributors](https://github.com/ant-design/ant-design/issues/3222), The Collaborators will then start the voting process, and after passing the voting, they will invite you to officially become a Collaborator at Ant Design. After you become a newly appointed Ant Design collaborator, you will be assigned some additional rights, such as: - Tag the issue - Close the issue - Free to create branches under the Ant Design project - Free to merge approved PR - ... There are some caveats to this. ### Merge PR It's time to merge PR! Ant Design uses both squash merge and commit merge in different case which requires attention. Following is some introduction about the difference: ![008](https://user-images.githubusercontent.com/10286961/224358476-2332e36f-0adf-486f-8b17-1b2ad34926aa.jpg) - **Merge pull request**: Merge the current PR into the target branch normally (usually used when branches merge with each other, and commit records will not be merged. Do not use this when merging PRs, otherwise too many redundant commit records will be added to the target branch). - **Squash and merge**: Merge the commit record into one and merge it into the target branch (this is usually used for merging PRs). - **Rebase and merge**：When you want to adjust the baseline Merge in Ant Design requires at least one collaborator's approve. Collaborator who approved should ensure PR are fully reviewed and confirm. ### Identify XY Problems During routine maintenance, some issues can easily reproduce but some others are not. Report sometimes get stuck in XY problem which makes requirement or bug question strange to understand. Thus, before resolving the superficial problems, we should dig into the real question. - [X-Y PROBLEM](https://xyproblem.info/) ## Epilogue Hoping that more and more contributors and collaborators will join us to build a more efficient and elegant Ant Design. --- Title: Extends Theme URL: https://ant.design/docs/blog/config-provider-style --- Ant Design v5 provides the Design Token model, which supports custom algorithm to implement theme extension capabilities. For example, the compact theme itself does not carry color style algorithms, so it can be implemented by passing in multiple algorithms to achieve the compact theme under the light theme and the compact theme under the dark theme. Today, we now put down the algorithm part. Talk about how to extend the theme through ConfigProvider. ## An Example This is an example of using ConfigProvider to extend the theme. You can view the complete code directly [here](https://github.com/zombieJ/antd-geek-theme-sample) ([online demo](https://zombiej.github.io/antd-geek-theme-sample/demos/theme)): ![Geek Theme](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*i3kvR6-tozgAAAAAAAAAAAAADrJ8AQ/original) We will talk about how to use ConfigProvider to extend the theme in Ant Design. Of course, this article is not a CSS tutorial, so we will not introduce the style implementation above. If you are interested, you can directly look at the code instead. ## Limitation of Token Design Token has powerful extension capabilities, but it also has limitations. For example, when Token does not support some configurations, developers become powerless. Even worse, some theme implementations cannot rely solely on a certain Token, which will become very difficult. For example, the gradient border colors in the above example cannot be implemented simply by `border-color`, it requires some CSS tricks. As mentioned in ["Happy Work Theme"](/docs/blog/happy-work), landing some specific implementations to Design Token will cause the code quality to deteriorate rapidly. Therefore, we need some other ways to extend the theme, which can uniformly modify the style of a component. And ConfigProvider is such an entry. ## ConfigProvider In `5.7.0`, ConfigProvider supports the `className` and `style` configurations of all components. So we can easily extend beyond Token: ```tsx ``` And then we can go to add our style: ```less .my-button { background: red; } ``` This is actually strange. Since we can modify the style through `className`, why do we need ConfigProvider? We can just override the `.ant-btn` style. If your project is maintained by only one person, this is a good idea. But if your project is a large project, then you will find that this approach will cause style conflicts. Especially in the case of multi-person collaboration, modifying styles at will will result in unexpected results, and other people have to use more complex selectors to override your styles. ConfigProvider can solve this problem well. It can isolate styles inside ConfigProvider and will not affect other components. ## Theme Extension Above example looks easy to implement, but in real scenarios you will find that there are some shortcomings for hierarchical structures. For example, the `ant-` prefix can be modified by ConfigProvider's `prefixCls`, so the prefix of the semantic structure may change from `ant-btn-icon` to `abc-btn-icon`. So it is not enough to override only by `my-button`: ```less .my-button { // OPS. It's `abc-btn-icon` now. .ant-btn-icon { background: red; } } ``` So our extended theme also needs the ability to consume `prefixCls`. In CSS-in-JS, mixing `prefixCls` is easy. We can get `prefixCls` through the `getPrefixCls` method of ConfigProvider, and then mix it: ```tsx // This is an example of using `antd-style`, you can use any CSS-in-JS library. import React from 'react'; import { ConfigProvider } from 'antd'; import { createStyles } from 'antd-style'; const useButtonStyle = createStyles(({ css }, prefixCls: string) => { return { btn: css` background: red; .${prefixCls}-icon { color: green; } `, }; }); const GeekProvider: React.FC> = (props) => { const { getPrefixCls } = React.useContext(ConfigProvider.ConfigContext); const btnPrefixCls = getPrefixCls('btn'); const { styles } = useButtonStyle(btnPrefixCls); return {props.children}; }; export default GeekProvider; ``` Red Button It's also easy to extend for scenarios that need to inherit `className`: ```tsx import React from 'react'; import { ConfigProvider } from 'antd'; import classNames from 'classnames'; const GeekProvider: React.FC> = (props) => { const { button, getPrefixCls } = React.useContext(ConfigProvider.ConfigContext); const btnPrefixCls = getPrefixCls('btn'); const { styles } = useButtonStyle(btnPrefixCls); return ( {props.children} ); }; export default GeekProvider; ``` ## Summary Through ConfigProvider, we can further extend the theme. It can isolate styles well and avoid style conflicts. Let's try it out! --- Title: Color Models and Color Picker URL: https://ant.design/docs/blog/color-picker --- Hello everyone, I'm [Redjue](https://github.com/Redjue), and I'm honored to have the opportunity to contribute the [ColorPicker](/components/color-picker) component to **Ant Design** this year. It's been a great learning experience and has given me a deeper understanding of the development process of **Ant Design**. In this article, I will share the specific implementation process. ## Color Models Before we start implementing, we need to understand a concept: color models. A color model is a mathematical model used to describe colors. Common color models include `RGB`, `HSV`, `HEX`, etc. Among these color models, `RGB` is the most common and easiest to understand, so let's start with the `RGB` color model. ### RGB Color Model The `RGB` color model represents colors by the combination of three primary colors (red, green, and blue). The value range of each primary color is 0-255, and the combination of the three primary colors can represent 2563 colors. These colors can form a cube, as shown in the following figure: ![RGB](https://user-images.githubusercontent.com/21119589/268834307-79fca808-d3a3-4fe8-b370-ea1ec472023c.png) In the `RGB` color model, each color can be represented by a triplet `(R, G, B)`, where `R` represents the value of red, `G` represents the value of green, and `B` represents the value of blue. For example, red can be represented as `rgb(255, 0, 0)`, green can be represented as `rgb(0, 255, 0)`, and blue can be represented as `rgb(0, 0, 255)`. ### HSV/HSB Color Model The `HSV` color model represents colors by hue, saturation, and value. The value range of hue is 0-360, and the value range of saturation and value is 0-100. The `HSV` color model can be represented by a cone, as shown in the following figure: ![HSV](https://user-images.githubusercontent.com/21119589/268834741-83940b90-c709-492b-8a7e-f59d317411e9.png) In the `HSV` color model, each color can be represented by a triplet `(H, S, V)`, where `H` represents the value of hue, `S` represents the value of saturation, and `V` represents the value of value. For example, red can be represented as `hsv(0, 100, 100)`, green can be represented as `hsv(120, 100, 100)`, and blue can be represented as `hsv(240, 100, 100)`. ### HEX Color Model The `HEX` color model represents colors by hexadecimal numbers. The first two digits represent the value of red, the middle two digits represent the value of green, and the last two digits represent the value of blue. For example, red can be represented as `#FF0000`, green can be represented as `#00FF00`, and blue can be represented as `#0000FF`. As shown in the following figure: ![HEX](https://user-images.githubusercontent.com/21119589/268841812-1b8310f5-322b-45ec-b768-d4115cf7091d.png) This is also the most common way of representing colors because it can be used directly in CSS. Moreover, the representation is very simple, just convert the three numbers in the RGB color model to hexadecimal numbers. ## Conversion of Color Models Different algorithms are needed for the conversion of color models. There are many mature libraries on the market that can be selected. In the implementation, we chose the library [tinycolor](https://github.com/scttcper/tinycolor), which supports the conversion of multiple color models such as `RGB`, `HSL`, `HSV`, `HEX`, etc. Moreover, its size is very small, only about 10KB, which is very suitable for use in browsers. ## Selection of Color Models Since we need to implement a color picker, we need to choose a color model to represent colors. In terms of complexity, the `RGB` color model is the simplest because it only needs three numbers to represent a color, and its value range is 0-255, which is very easy to understand. However, the disadvantage of the `RGB` color model is also very obvious. Its color space is a cube, and the color change at the edge of the cube is very obvious. This color space is not suitable for human visual perception. Therefore, we need to choose a color model that is more suitable for human visual perception. Here we chose the `HSV` color model, which represents colors through hue, saturation, and value. This color space is more in line with human visual perception, and the color change at the edge of the color space is not too obvious. ## Implementation Details The implementation mainly consists of three parts: the color panel, the selection anchor, and sliders. ### Color Panel Since we are using the `HSV` color model, we need to represent hue, saturation, and value on the panel. 1. Hue ```css background-color: rgb(0, 106, 255); ``` This way we get a blue color with both saturation and brightness set to 100% 2. Add brightness overlay ```css background-color: rgb(0, 106, 255); background-image: linear-gradient(0deg, rgb(0, 0, 0), transparent); ``` After adding the brightness overlay, we get a blue color with brightness variation 3. Add saturation overlay ```css background-color: rgb(0, 106, 255); background-image: linear-gradient(0deg, rgb(0, 0, 0), transparent), linear-gradient(90deg, rgb(255, 255, 255), rgba(255, 255, 255, 0)); ``` After adding the saturation overlay, we get a blue color with brightness variation So far, we have obtained a color panel with complete hue, saturation, and brightness. ### Selection Anchor The implementation of the selection anchor is relatively simple. We only need to correspond the offset position of the anchor to the saturation and brightness of the color panel. ```ts ... const { width, height } = containerRef.current.getBoundingClientRect(); const { width: targetWidth, height: targetHeight } = targetRef.current.getBoundingClientRect(); const centerOffsetX = targetWidth / 2; const centerOffsetY = targetHeight / 2; // Saturation const saturation = (offset.x + centerOffsetX) / width; // Brightness const bright = 1 - (offset.y + centerOffsetY) / height; ``` ### Hue and Alpha Sliders The logic is the same as above, we just need to correspond the offset position of the sliders to the hue or alpha of the color. ```ts ... const { width, height } = containerRef.current.getBoundingClientRect(); const { width: targetWidth, height: targetHeight } = targetRef.current.getBoundingClientRect(); const centerOffsetX = targetWidth / 2; const centerOffsetY = targetHeight / 2; // Hue const hue = ((offset.x + centerOffsetX) / width) * 360; // Opacity const alpha = (offset.x + centerOffsetX) / width; ``` So far, we have obtained a color picker with complete hue, saturation, and brightness, as shown in the following figure: ## Summary Through this development journey, I have gained a deeper understanding of color models and the development process of Ant Design. Thanks to the Ant Design team for giving me this opportunity, and thank you all for reading. If you are interested in the implementation details, you can check out the source code implementation at [@rc-component/color-picker](https://github.com/react-component/color-picker). ## References - https://zh.wikipedia.org/wiki/%E4%B8%89%E5%8E%9F%E8%89%B2%E5%85%89%E6%A8%A1%E5%BC%8F#/media/File:RGB_color_solid_cube.png - https://zh.wikipedia.org/wiki/HSL%E5%92%8CHSV%E8%89%B2%E5%BD%A9%E7%A9%BA%E9%97%B4#/media/File:HSV_cone.png - https://zh.wikipedia.org/wiki/%E7%BD%91%E9%A1%B5%E9%A2%9C%E8%89%B2#/media/File:Web_Color_Charts.svg --- Title: Tree's check conduction URL: https://ant.design/docs/blog/check-conduct --- In the Tree or similar components (such as TreeSelect, Cascader), needs check function. It's unambiguous most of the time, but when a `disabled` node appears somewhere in the middle, it's worth talking about. This article will introduce the logic of check conduction in antd. It should be noted that in different scenarios, there will be various requirements, and antd has chosen the most commonly used check conduction logic. If you need a different custom style, you can implement it yourself through `checkStrictly`. ## Some conduction strategies Before we start, let's establish a consensus. That is, when a node is `disabled`, it cannot be clicked `checked`. Then we take the following Tree structure as an example: Tree Next, we check the root node `parent 1`, and analyze the similarities and differences of different check transmission strategies. ### All nodes will be checked This is the most intuitive strategy, all nodes will be checked: Tree You can immediately see the problem with this strategy, we mentioned earlier that `disabled` nodes are not allowed to be `checked`. But when the parent node is not `disabled`, its child nodes will be forcibly checked. This will cause the `disabled` node to "can" be checked, which is obviously unreasonable. ### All checkable nodes are checked Tree From the checkbox interaction, it looks good, but it's not intuitive. After `parent 1` is checked, `leaf 2` is checked by conduction. But the middle node `parent 1-0` is not checked. At some deep enough level, this strategy can cause the user to be unaware that a check has been propagated: Tree When there is no scrolling, the user can't realize that the upper `disabled` is not checked, but the top is checked: Tree ### Check only reachable checkable nodes This is also the current strategy of antd, when a node is checked, it will propagate upwards and downwards from the node until `disabled` stops. When there are multiple `disabled` in the node, they will each check the status management: Tree Conversely check `leaf 2`, it will not conduct: Tree The advantage of this strategy is that users can clearly see the selection process. Compared with the previous strategy, users only need a small area to understand the check logic in the scrolling scene. ## Some implementation details Note: We only introduce simple conduction logic here. Please refer to [actual code](https://github.com/react-component/tree/blob/62e0bf0b91d86b6e42fee69870ada9a4640b6c6f/src/utils/conductUtil.ts) for real world apply. Some performance optimizations will also be done, such as skipping nodes that have been traversed through the cache mechanism. ### Check conduction When a node is checked, we will add `key` to `checkedKeys`. We iterate over each `key` in the new `checkedKeys` for conduction checks. The first step will be conduction from top to bottom (in the example below we check `0-0`): Tree We record the current node `0-0` and the transmitted `0-0-0` and `0-0-1`: Tree In the second step, we will conduct upwards from this node: Tree Similarly, record the node `0` that was passed on: Tree When the parent node is checked, the parent node of the parent node may also be checked, so we need to continue to conduct upward until the root node or `disabled` node. ### Uncheck conduction Same as above, we will perform conduction traversal up and down, and then remove the conduction node from `checkedKeys`. Therefore no further repetition. ## Finally Before the early days of v3, we encountered that the `disabled` check of Tree has different appeals in different scenarios (and each of them is "reasonable" when viewing fragmented appeals), and when it is extracted for inspection, We found that these fragmented demands can conflict with each other. Therefore, we sorted out its transmission logic and chose the most intuitive strategy. Of course, if the current implementation does not meet the requirements, you can implement it yourself through `checkStrictly`. --- Title: A build ghost URL: https://ant.design/docs/blog/build-ghost --- In the maintenance of antd-mobile, We meet an annoying ghost. It rarely appears when building locally, but it almost always appears in the github workflow. After a lot of tossing, We finally found its trace. ### CI Failed...again For antd-mobile's CI, there is a task to check the build artifacts, which will prompt the file size changes. But in recent months, this task often fails to build, as shown in the following figure: ![CI failed](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*XSAESJ3_HWgAAAAAAAAAAAAADrJ8AQ/original) Check the log, we will get the error message of CSS file: ![Unknown word](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*2ybATYq9l2oAAAAAAAAAAAAADrJ8AQ/original) It seems that the error occurred when building 2x style (antd-mobile will generate 2x style for high-definition screen): ```log [09:44:16] Using gulpfile ~/work/ant-design-mobile/ant-design-mobile/gulpfile.js [09:44:16] Starting 'default'... [09:44:16] Starting 'clean'... [09:44:17] Finished 'clean' after 286 ms [09:44:17] Starting 'buildES'... [09:44:26] Finished 'buildES' after 8.77 s [09:44:26] Starting 'buildCJS'... [09:44:27] Finished 'buildCJS' after 1.72 s [09:44:27] Starting 'buildDeclaration'... [09:44:27] Starting 'buildStyle'... [09:44:28] Finished 'buildStyle' after 682 ms [09:44:34] Finished 'buildDeclaration' after 6.5 s [09:44:34] Starting 'copyAssets'... [09:44:34] Finished 'copyAssets' after 2.37 ms [09:44:34] Starting 'copyMetaFiles'... [09:44:34] Finished 'copyMetaFiles' after 4.64 ms [09:44:34] Starting 'generatePackageJSON'... [09:44:34] Finished 'generatePackageJSON' after 2.72 ms [09:44:34] Starting 'buildBundles'... [09:44:45] Finished 'buildBundles' after 11 s [09:44:45] Starting 'init2xFolder'... [09:44:46] Finished 'init2xFolder' after 811 ms [09:44:46] Starting 'build2xCSS'... [09:44:46] 'build2xCSS' errored after 126 ms [09:44:46] CssSyntaxError in plugin "gulp-postcss" ``` The `style.css` of `build2xCSS` comes from the artifact of `buildStyle`, so it can be determined that there is a problem in the `buildStyle` task. After checking the corresponding file `/lib/bundle/style.css`, we found the following content: ![Break Lines](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*5NqFR6_nkhwAAAAAAAAAAAAADrJ8AQ/original) The first line of `style.css` is the compressed style, and then the incomplete uncompressed style. Compared with the successful artifact, it will be found that the style after the second line is unexpected: ![Success Style](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*xnDRT5SDVvMAAAAAAAAAAAAADrJ8AQ/original) Check the uncompressed content, we will find that these contents already exist in the previous compressed content: ![Duplicated Content](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*wShGRJ16U1AAAAAAAAAAAAAADrJ8AQ/original) It is speculated that the uncompressed content was generated first during the build, and then the compressed operation was performed. But there is an asynchronous problem, the second task started to execute before the first task was completed, resulting in the duplication of content. What's even more bizarre is that if it is an asynchronous problem, the error file content generated on CI is surprisingly consistent. No matter how many times it is built, as long as it fails, it must be the same content. ### Concurrent problem Check the `gulpfile.js` file, we found that `buildStyle` uses vite to build. Considering that it may be a problem with the build version, so we upgraded vite from `3.x` to `5.x`, but the problem still exists. So check the relevant configuration: ```tsx { root: process.cwd(), mode: env, logLevel: 'silent', define: { 'process.env.NODE_ENV': `"${env}"` }, build: { cssTarget: 'chrome61', lib: { formats, ... }, rollupOptions: { output: { dir: './lib/bundle', globals: { 'react': 'React', 'react-dom': 'ReactDOM', }, }, }, minify: isProd ? 'esbuild' : false, }, } ``` Though closing the `logLevel: 'silent'` configuration, we can see more log content after rebuilding: ![Bundle Result](https://mdn.alipayobjects.com/huamei_7uahnr/afts/img/A*efjVR4DG_ysAAAAAAAAAAAAADrJ8AQ/original) We are close. When building, antd-mobile will create three copies of `es`, `cjs`, and `umd` through `lib.formats`. And each `format` will generate a `style.css` file. If it is just to overwrite the file, it should only waste extra build resources, and the compressed `style.css` will always be overwritten, and there should be no problem of simultaneous overwriting. Let's check the part that calls vite to build: ```tsx async function buildBundles(cb) { const envs = ['development', 'production']; const configs = envs.map((env) => getViteConfigForPackage({ env, formats: ['es', 'cjs', 'umd'], external: ['react', 'react-dom'], }), ); await Promise.all(configs.map((config) => vite.build(config))); cb && cb(); } ``` That's it. `Promise.all` is used to build concurrently, and vite's build is asynchronous. This causes a competition problem for `style.css`. The rollup called by vite will clean up the files and then perform write operations. Since the compressed style needs to be uglified, it is always slower than the uncompressed version. When rollup has finished cleaning and starts writing files, although the first part of the uncompressed version is deleted due to cleaning, the subsequent content is still written, while the compressed version starts writing from the beginning. When both are written, an error will occur and the content will be consistent under each CI build. The fix is also very simple, just change it to sequential execution: ```tsx for (const config of configs) { await vite.build(config); } ``` (Of course, subsequent optimizations are also needed for the script. Skip the unnecessary `style.css` generation) ### That's all With the performance changes of github CI, the ghost that was originally difficult to encounter has become stable and reproducible, which is quite interesting. This also gives us the opportunity to locate the problem. --- Title: Watermark URL: https://ant.design/components/watermark --- ## When To Use - Use when the page needs to be watermarked to identify the copyright. - Suitable for preventing information theft. ## Examples Basic Multi-line watermark Image watermark Custom configuration Modal or Drawer ## API Common props ref：[Common props](/docs/react/common-props) > This component is available since `antd@5.1.0`. ### Watermark | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | width | The width of the watermark, the default value of `content` is its own width | number | 120 | | | height | The height of the watermark, the default value of `content` is its own height | number | 64 | | | inherit | Pass the watermark to the pop-up component such as Modal, Drawer | boolean | true | 5.11.0 | | rotate | When the watermark is drawn, the rotation Angle, unit `°` | number | -22 | | | zIndex | The z-index of the appended watermark element | number | 9 | | | image | Image source, it is recommended to export 2x or 3x image, high priority (support base64 format) | string | - | | | content | Watermark text content | string \| string[] | - | | | font | Text style | [Font](#font) | [Font](#font) | | | gap | The spacing between watermarks | \[number, number\] | \[100, 100\] | | | offset | The offset of the watermark from the upper left corner of the container. The default is `gap/2` | \[number, number\] | \[gap\[0\]/2, gap\[1\]/2\] | | ### Font | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | color | font color | [CanvasFillStrokeStyles.fillStyle](https://developer.mozilla.org/docs/Web/API/CanvasRenderingContext2D/fillStyle) | rgba(0,0,0,.15) | | | fontSize | font size | number | 16 | | | fontWeight | font weight | `normal` \| `light` \| `weight` \| number | normal | | | fontFamily | font family | string | sans-serif | | | fontStyle | font style | `none` \| `normal` \| `italic` \| `oblique` | normal | | | textAlign | specify the text alignment direction | [CanvasTextAlign](https://developer.mozilla.org/docs/Web/API/CanvasRenderingContext2D/textAlign) | `center` | 5.10.0 | ## Design Token ## FAQ ### Handle abnormal image watermarks When using an image watermark and the image loads abnormally, you can add `content` at the same time to prevent the watermark from becoming invalid (since 5.2.3). ```typescript jsx
    ``` ### Why `overflow: hidden` style is added since version 5.18.0? User can hide the watermark by setting the container height to 0 through the developer tool in the previous version. To avoid this situation, we added the `overflow: hidden` style to the container. When the container height changes, the content is also hidden. You can override the style to modify this behavior: ```tsx ``` --- Title: Upload URL: https://ant.design/components/upload --- ## When To Use Uploading is the process of publishing information (web pages, text, pictures, video, etc.) to a remote server via a web page or upload tool. - When you need to upload one or more files. - When you need to show the process of uploading. - When you need to upload files by dragging and dropping. ## Examples Upload by clicking Avatar Default Files Pictures Wall Pictures with picture-circle type Complete control over file list Drag and Drop Paste Upload directory Upload manually Upload png file only Pictures with list style Customize preview file Max Count Transform file before request Aliyun OSS custom show icon Custom action icon and extra info Drag sorting of uploadList Crop image before uploading Customize Progress Bar Component Token Debug Disabled Styles ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | accept | File types that can be accepted. See [input accept Attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#accept) | string | - | | | action | Uploading URL | string \| (file) => Promise<string> | - | | | beforeUpload | Hook function which will be executed before uploading. Uploading will be stopped with `false` or a rejected Promise returned. When returned value is `Upload.LIST_IGNORE`, the list of files that have been uploaded will ignore it. **Warning：this function is not supported in IE9** | (file, fileList) => boolean \| Promise<File> \| `Upload.LIST_IGNORE` | - | | | customRequest | Override for the default xhr behavior allowing for additional customization and the ability to implement your own XMLHttpRequest | function | - | | | data | Uploading extra params or function which can return uploading extra params | object \| (file) => object \| Promise<object> | - | | | defaultFileList | Default list of files that have been uploaded | object\[] | - | | | directory | Support upload whole directory ([caniuse](https://caniuse.com/#feat=input-file-directory)) | boolean | false | | | disabled | Disable upload button | boolean | false | When customizing Upload children, please pass the disabled attribute to the child node at the same time to ensure the disabled rendering effect is consistent. | | fileList | List of files that have been uploaded (controlled). Here is a common issue [#2423](https://github.com/ant-design/ant-design/issues/2423) when using it | [UploadFile](#uploadfile)\[] | - | | | headers | Set request headers, valid above IE10 | object | - | | | iconRender | Custom show icon | (file: UploadFile, listType?: UploadListType) => ReactNode | - | | | isImageUrl | Customize if render <img /> in thumbnail | (file: UploadFile) => boolean | [(inside implementation)](https://github.com/ant-design/ant-design/blob/4ad5830eecfb87471cd8ac588c5d992862b70770/components/upload/utils.tsx#L47-L68) | | | itemRender | Custom item of uploadList | (originNode: ReactElement, file: UploadFile, fileList: object\[], actions: { download: function, preview: function, remove: function }) => React.ReactNode | - | 4.16.0 | | listType | Built-in stylesheets, support for four types: `text`, `picture`, `picture-card` or `picture-circle` | string | `text` | `picture-circle`(5.2.0+) | | maxCount | Limit the number of uploaded files. Will replace current one when `maxCount` is `1` | number | - | 4.10.0 | | method | The http method of upload request | string | `post` | | | multiple | Whether to support selected multiple files. `IE10+` supported. You can select multiple files with CTRL holding down while multiple is set to be true | boolean | false | | | name | The name of uploading file | string | `file` | | | openFileDialogOnClick | Click open file dialog | boolean | true | | | pastable | Support paste file | boolean | false | 5.25.0 | | previewFile | Customize preview file logic | (file: File \| Blob) => Promise<dataURL: string> | - | | | progress | Custom progress bar | [ProgressProps](/components/progress/#api) (support `type="line"` only) | { strokeWidth: 2, showInfo: false } | 4.3.0 | | showUploadList | Whether to show default upload list, could be an object to specify `extra`, `showPreviewIcon`, `showRemoveIcon`, `showDownloadIcon`, `removeIcon` and `downloadIcon` individually | boolean \| { extra?: ReactNode \| (file: UploadFile) => ReactNode, showPreviewIcon?: boolean \| (file: UploadFile) => boolean, showDownloadIcon?: boolean \| (file: UploadFile) => boolean, showRemoveIcon?: boolean \| (file: UploadFile) => boolean, previewIcon?: ReactNode \| (file: UploadFile) => ReactNode, removeIcon?: ReactNode \| (file: UploadFile) => ReactNode, downloadIcon?: ReactNode \| (file: UploadFile) => ReactNode } | true | `extra`: 5.20.0, `showPreviewIcon` function: 5.21.0, `showRemoveIcon` function: 5.21.0, `showDownloadIcon` function: 5.21.0 | | withCredentials | The ajax upload with cookie sent | boolean | false | | | onChange | A callback function, can be executed when uploading state is changing. It will trigger by every uploading phase. see [onChange](#onchange) | function | - | | | onDrop | A callback function executed when files are dragged and dropped into the upload area | (event: React.DragEvent) => void | - | 4.16.0 | | onDownload | Click the method to download the file, pass the method to perform the method logic, and do not pass the default jump to the new TAB | function(file): void | (Jump to new TAB) | | | onPreview | A callback function, will be executed when the file link or preview icon is clicked | function(file) | - | | | onRemove | A callback function, will be executed when removing file button is clicked, remove event will be prevented when the return value is false or a Promise which resolve(false) or reject | function(file): boolean \| Promise | - | | ### UploadFile Extends File with additional props. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | crossOrigin | CORS settings attributes | `'anonymous'` \| `'use-credentials'` \| `''` | - | 4.20.0 | | name | File name | string | - | - | | percent | Upload progress percent | number | - | - | | status | Upload status. Show different style when configured | `error` \| `done` \| `uploading` \| `removed` | - | - | | thumbUrl | Thumb image url | string | - | - | | uid | unique id. Will auto-generate when not provided | string | - | - | | url | Download url | string | - | - | ### onChange > 💡 The function will be called when uploading is in progress, completed, or failed. When uploading state change, it returns: ```jsx { file: { /* ... */ }, fileList: [ /* ... */ ], event: { /* ... */ }, } ``` 1. `file` File object for the current operation. ```jsx { uid: 'uid', // unique identifier, negative is recommended, to prevent interference with internally generated id name: 'xx.png', // file name status: 'done' | 'uploading' | 'error' | 'removed', // Intercepted file by beforeUpload doesn't have a status field. response: '{"status": "success"}', // response from server linkProps: '{"download": "image"}', // additional HTML props of file link xhr: 'XMLHttpRequest{ ... }', // XMLHttpRequest Header } ``` 2. `fileList` current list of files 3. `event` response from the server, including uploading progress, supported by advanced browsers. ## Semantic DOM ## Design Token ## FAQ ### How do I implement upload server side? - You can consult [jQuery-File-Upload](https://github.com/blueimp/jQuery-File-Upload/wiki#server-side) about how to implement server side upload interface. - There is a mock example of [express](https://github.com/react-component/upload/blob/211979fdaa2c7896b6496df7061a0cfc0fc5434e/server.js) in rc-upload. ### I want to display download links. Please set property `url` of each item in `fileList` to control the content of the link. ### How to use `customRequest`? See . ### Why will the `fileList` that's in control not trigger `onChange` `status` update when the file is not in the list? `onChange` will only trigger when the file is in the list, it will ignore any events removed from the list. Please note that there does exist a bug which makes an event still trigger even when the file is not in the list before `4.13.0`. ### Why does `onChange` sometimes return File object and other times return { originFileObj: File }? For compatible case, we return File object when `beforeUpload` return `false`. It will merge to `{ originFileObj: File }` in the next major version. Current version is compatible to get origin file by `info.file.originFileObj`. You can change this before a major release. ### Why sometimes Chrome can not upload? Chrome update will also break native upload. Please restart Chrome to finish the upload job. click restart button on Chrome Ref: - [#48007](https://github.com/ant-design/ant-design/issues/48007) - [#32672](https://github.com/ant-design/ant-design/issues/32672) - [#32913](https://github.com/ant-design/ant-design/issues/32913) - [#33988](https://github.com/ant-design/ant-design/issues/33988) ### Can still select files when uploading a folder in Safari? Inside the upload component, we use the `directory` and `webkitdirectory` properties to control only directories can be selected. However, in Safari's implementation it doesn't seem to work. See [here](https://stackoverflow.com/q/55649945/3040605). Please try passing an additional `accept` attribute that cannot match any files. For example: ```jsx accept: `.${'n'.repeat(100)}`; ``` --- Title: Typography URL: https://ant.design/components/typography --- ## When To Use - When you need to display a title or paragraph contents in Articles/Blogs/Notes. - When you need copyable/editable/ellipsis texts. ## Examples Basic Title Component Title and Paragraph Text and Link Component Editable Copyable Ellipsis Controlled ellipsis expand/collapse Ellipsis from middle Ellipsis Debug suffix Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Typography.Text | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | code | Code style | boolean | false | | | copyable | Whether to be copyable, customize it via setting an object | boolean \| [copyable](#copyable) | false | | | delete | Deleted line style | boolean | false | | | disabled | Disabled content | boolean | false | | | editable | If editable. Can control edit state when is object | boolean \| [editable](#editable) | false | | | ellipsis | Display ellipsis when text overflows, can't configure expandable, rows and onExpand by using object. Diff with Typography.Paragraph, Text do not have 100% width style which means it will fix width on the first ellipsis. If you want to have responsive ellipsis, please set width manually | boolean \| [Omit](#ellipsis) | false | | | keyboard | Keyboard style | boolean | false | 4.3.0 | | mark | Marked style | boolean | false | | | onClick | Set the handler to handle click event | (event) => void | - | | | strong | Bold style | boolean | false | | | italic | Italic style | boolean | false | 4.16.0 | | type | Content type | `secondary` \| `success` \| `warning` \| `danger` | - | success: 4.6.0 | | underline | Underlined style | boolean | false | | ### Typography.Title | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | code | Code style | boolean | false | | | copyable | Whether to be copyable, customize it via setting an object | boolean \| [copyable](#copyable) | false | | | delete | Deleted line style | boolean | false | | | disabled | Disabled content | boolean | false | | | editable | If editable. Can control edit state when is object | boolean \| [editable](#editable) | false | | | ellipsis | Display ellipsis when text overflows, can configure rows and expandable by using object | boolean \| [ellipsis](#ellipsis) | false | | | level | Set content importance. Match with `h1`, `h2`, `h3`, `h4`, `h5` | number: 1, 2, 3, 4, 5 | 1 | 5: 4.6.0 | | mark | Marked style | boolean | false | | | onClick | Set the handler to handle click event | (event) => void | - | | | italic | Italic style | boolean | false | 4.16.0 | | type | Content type | `secondary` \| `success` \| `warning` \| `danger` | - | success: 4.6.0 | | underline | Underlined style | boolean | false | | ### Typography.Paragraph | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | code | Code style | boolean | false | | | copyable | Whether to be copyable, customize it via setting an object | boolean \| [copyable](#copyable) | false | | | delete | Deleted line style | boolean | false | | | disabled | Disabled content | boolean | false | | | editable | If editable. Can control edit state when is object | boolean \| [editable](#editable) | false | | | ellipsis | Display ellipsis when text overflows, can configure rows and expandable by using object | boolean \| [ellipsis](#ellipsis) | false | | | mark | Marked style | boolean | false | | | onClick | Set the handler to handle click event | (event) => void | - | | | strong | Bold style | boolean | false | | | italic | Italic style | boolean | false | 4.16.0 | | type | Content type | `secondary` \| `success` \| `warning` \| `danger` | - | success: 4.6.0 | | underline | Underlined style | boolean | false | | ### copyable { text: string | (() => string | Promise), onCopy: function(event), icon: ReactNode, tooltips: false | [ReactNode, ReactNode], format: 'text/plain' | 'text/html', tabIndex: number, } | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | format | The Mime Type of the text | 'text/plain' \| 'text/html' | - | 4.21.0 | | icon | Custom copy icon: \[copyIcon, copiedIcon] | \[ReactNode, ReactNode] | - | 4.6.0 | | text | The text to copy | string | - | | | tooltips | Custom tooltip text, hide when it is false | \[ReactNode, ReactNode] | \[`Copy`, `Copied`] | 4.4.0 | | onCopy | Called when copied text | function | - | | | tabIndex | Set tabIndex of the copy button | number | 0 | 5.17.0 | ### editable { icon: ReactNode, tooltip: ReactNode, editing: boolean, maxLength: number, autoSize: boolean | { minRows: number, maxRows: number }, text: string, onChange: function(string), onCancel: function, onStart: function, onEnd: function, triggerType: ('icon' | 'text')[], enterIcon: ReactNode, tabIndex: number, } | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoSize | `autoSize` attribute of textarea | boolean \| { minRows: number, maxRows: number } | - | 4.4.0 | | editing | Whether to be editable | boolean | false | | | icon | Custom editable icon | ReactNode | <EditOutlined /> | 4.6.0 | | maxLength | `maxLength` attribute of textarea | number | - | 4.4.0 | | tooltip | Custom tooltip text, hide when it is false | ReactNode | `Edit` | 4.6.0 | | text | Edit text, specify the editing content instead of using the children implicitly | string | - | 4.24.0 | | onChange | Called when input at textarea | function(value: string) | - | | | onCancel | Called when type ESC to exit editable state | function | - | | | onStart | Called when enter editable state | function | - | | | onEnd | Called when type ENTER to exit editable state | function | - | 4.14.0 | | triggerType | Edit mode trigger - icon, text or both (not specifying icon as trigger hides it) | Array<`icon`\|`text`> | \[`icon`] | | | enterIcon | Custom "enter" icon in the edit field (passing `null` removes the icon) | ReactNode | `` | 4.17.0 | | tabIndex | Set tabIndex of the edit button | number | 0 | 5.17.0 | ### ellipsis ```tsx interface EllipsisConfig { rows: number; /** `collapsible` added in `5.16.0` */ expandable: boolean | 'collapsible'; suffix: string; /** render function added in `5.16.0` */ symbol: ReactNode | ((expanded: boolean) => ReactNode); tooltip: ReactNode | TooltipProps; /** added in `5.16.0` */ defaultExpanded: boolean; /** added in `5.16.0` */ expanded: boolean; /** `info` added in `5.16.0` */ onExpand: (event: MouseEvent, info: { expanded: boolean }) => void; onEllipsis: (ellipsis: boolean) => void; } ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | expandable | Whether to be expandable | boolean \| 'collapsible' | - | `collapsible`: 5.16.0 | | rows | Max rows of content | number | - | | | suffix | Suffix of ellipsis content | string | - | | | symbol | Custom description of ellipsis | ReactNode \| ((expanded: boolean) => ReactNode) | `Expand` `Collapse` | | | tooltip | Show tooltip when ellipsis | ReactNode \| [TooltipProps](/components/tooltip/#api) | - | 4.11.0 | | defaultExpanded | Default expand or collapse | boolean | | 5.16.0 | | expanded | Expand or Collapse | boolean | | 5.16.0 | | onEllipsis | Called when enter or leave ellipsis state | function(ellipsis) | - | 4.2.0 | | onExpand | Called when expand content | function(event, { expanded: boolean }) | - | `info`: 5.16.0 | ## Design Token ## FAQ ### How to use Typography.Link in react-router? `react-router` support [customize](https://github.com/ReactTraining/react-router/blob/master/packages/react-router-dom/docs/api/Link.md#component-reactcomponent) render component: ```tsx ``` **Note：** This is not equivalent to the execution logic of react-router's Link [reference](https://github.com/ant-design/ant-design/pull/26737/files#r488769888) --- Title: TreeSelect URL: https://ant.design/components/tree-select --- ## When To Use `TreeSelect` is similar to `Select`, but the values are provided in a tree like structure. Any data whose entries are defined in a hierarchical manner is fit to use this control. Examples of such case may include a corporate hierarchy, a directory structure, and so on. ## Examples Basic Multiple Selection Generate from tree data Checkable Asynchronous loading Show Tree Line Placement Variants Status Max Count Prefix and Suffix _InternalPanelDoNotUseOrYouWillBeFired Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Tree props | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Customize clear icon | boolean \| { clearIcon?: ReactNode } | false | 5.8.0: Support object type | | ~~autoClearSearchValue~~ | If auto clear search input value when multiple select is selected/deselected | boolean | true | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.25.0 | | defaultOpen | Initial open state of dropdown | boolean | - | | | defaultValue | To set the initial selected treeNode(s) | string \| string\[] | - | | | disabled | Disabled or not | boolean | false | | | ~~popupClassName~~ | The className of dropdown menu, use `classNames.popup.root` instead | string | - | 4.23.0 | | popupMatchSelectWidth | Determine whether the popup menu and the select input are the same width. Default set `min-width` same as input. Will ignore when value less than select width. `false` will disable virtual scroll | boolean \| number | true | 5.5.0 | | ~~dropdownRender~~ | Customize dropdown content, use `popupRender` instead | (originNode: ReactNode, props) => ReactNode | - | | | popupRender | Customize dropdown content | (originNode: ReactNode, props) => ReactNode | - | | | ~~dropdownStyle~~ | To set the style of the dropdown menu, use `styles.popup.root` instead | CSSProperties | - | | | fieldNames | Customize node label, value, children field name | object | { label: `label`, value: `value`, children: `children` } | 4.17.0 | | ~~filterTreeNode~~ | Whether to filter treeNodes by input value. The value of `treeNodeFilterProp` is used for filtering by default | boolean \| function(inputValue: string, treeNode: TreeNode) (should return boolean) | function | | | getPopupContainer | To set the container of the dropdown menu. The default is to create a `div` element in `body`, you can reset it to the scrolling area and make a relative reposition. [example](https://codepen.io/afc163/pen/zEjNOy?editors=0010) | function(triggerNode) | () => document.body | | | labelInValue | Whether to embed label in value, turn the format of value from `string` to {value: string, label: ReactNode, halfChecked: string\[]} | boolean | false | | | listHeight | Config popup height | number | 256 | | | loadData | Load data asynchronously. Will not load when filtering. Check FAQ for more info | function(node) | - | | | maxTagCount | Max tag count to show. `responsive` will cost render performance | number \| `responsive` | - | responsive: 4.10 | | maxCount | The maximum number of items that can be selected. Only takes effect when `multiple=true`. If (`showCheckedStrategy = 'SHOW_ALL'` and `treeCheckStrictly` is disabled) or `showCheckedStrategy = 'SHOW_PARENT'` is used, `maxCount` will not take effect. | number | - | 5.23.0 | | maxTagPlaceholder | Placeholder for not showing tags | ReactNode \| function(omittedValues) | - | | | maxTagTextLength | Max tag text length to show | number | - | | | multiple | Support multiple or not, will be `true` when enable `treeCheckable` | boolean | false | | | notFoundContent | Specify content to show when no result matches | ReactNode | `Not Found` | | | open | Controlled open state of dropdown | boolean | - | | | placeholder | Placeholder of the select input | string | - | | | placement | The position where the selection box pops up | `bottomLeft` `bottomRight` `topLeft` `topRight` | bottomLeft | | | prefix | The custom prefix | ReactNode | - | 5.22.0 | | ~~searchValue~~ | Work with `onSearch` to make search value controlled | string | - | | | showCheckedStrategy | The way show selected item in box when `treeCheckable` set. **Default:** just show child nodes. **`TreeSelect.SHOW_ALL`:** show all checked treeNodes (include parent treeNode). **`TreeSelect.SHOW_PARENT`:** show checked treeNodes (just show parent treeNode) | `TreeSelect.SHOW_ALL` \| `TreeSelect.SHOW_PARENT` \| `TreeSelect.SHOW_CHILD` | `TreeSelect.SHOW_CHILD` | | | showSearch | Support search or not | boolean \| [Object](#showsearch) | single: false \| multiple: true | | | size | To set the size of the select input | `large` \| `middle` \| `small` | - | | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | suffixIcon | The custom suffix icon | ReactNode | `` | | | switcherIcon | Customize collapse/expand icon of tree node | ReactNode \| ((props: AntTreeNodeProps) => ReactNode) | - | renderProps: 4.20.0 | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.25.0 | | tagRender | Customize tag render when `multiple` | (props) => ReactNode | - | | | treeCheckable | Whether to show checkbox on the treeNodes | boolean | false | | | treeCheckStrictly | Whether to check nodes precisely (in the `checkable` mode), means parent and child nodes are not associated, and it will make `labelInValue` be true | boolean | false | | | treeData | Data of the treeNodes, manual construction work is no longer needed if this property has been set(ensure the Uniqueness of each value) | array<{ value, title, children, \[disabled, disableCheckbox, selectable, checkable] }> | \[] | | | treeDataSimpleMode | Enable simple mode of treeData. Changes the `treeData` schema to: \[{id:1, pId:0, value:'1', title:"test1",...},...] where pId is parent node's id). It is possible to replace the default `id` and `pId` keys by providing object to `treeDataSimpleMode` | boolean \| object<{ id: string, pId: string, rootPId: string }> | false | | | treeTitleRender | Customize tree node title render | (nodeData) => ReactNode | - | 5.12.0 | | treeDefaultExpandAll | Whether to expand all treeNodes by default | boolean | false | | | treeDefaultExpandedKeys | Default expanded treeNodes | string\[] | - | | | treeExpandAction | Tree title open logic when click, optional: false \| `click` \| `doubleClick` | string \| boolean | false | 4.21.0 | | treeExpandedKeys | Set expanded keys | string\[] | - | | | treeIcon | Shows the icon before a TreeNode's title. There is no default style; you must set a custom style for it if set to `true` | boolean | false | | | treeLoadedKeys | (Controlled) Set loaded tree nodes, work with `loadData` only | string[] | [] | | | treeLine | Show the line. Ref [Tree - showLine](/components/tree/#tree-demo-line) | boolean \| object | false | 4.17.0 | | ~~treeNodeFilterProp~~ | Will be used for filtering if `filterTreeNode` returns true | string | `value` | | | treeNodeLabelProp | Will render as content of select | string | `title` | | | value | To set the current selected treeNode(s) | string \| string\[] | - | | | variant | Variants of selector | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | virtual | Disable virtual scroll when set to false | boolean | true | 4.1.0 | | onChange | A callback function, can be executed when selected treeNodes or input value change | function(value, label, extra) | - | | | ~~onDropdownVisibleChange~~ | Called when dropdown open, use `onOpenChange` instead | function(open) | - | | | ~~onSearch~~ | A callback function, can be executed when the search input changes | function(value: string) | - | | | onSelect | A callback function, can be executed when you select a treeNode | function(value, node, extra) | - | | | onTreeExpand | A callback function, can be executed when treeNode expanded | function(expandedKeys) | - | | | onPopupScroll | Called when dropdown scrolls | (event: UIEvent) => void | - | 5.17.0 | ### showSearch | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoClearSearchValue | If auto clear search input value when multiple select is selected/deselected | boolean | true | | | filterTreeNode | Whether to filter treeNodes by input value. The value of `treeNodeFilterProp` is used for filtering by default | boolean \| function(inputValue: string, treeNode: TreeNode) (should return boolean) | function | | | searchValue | Work with `onSearch` to make search value controlled | string | - | | | treeNodeFilterProp | Will be used for filtering if `filterTreeNode` returns true | string | `value` | | | onSearch | A callback function, can be executed when the search input changes | function(value: string) | - | | ### Tree Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ### TreeNode props > We recommend you to use `treeData` rather than `TreeNode`, to avoid the trouble of manual construction. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | checkable | When Tree is checkable, set TreeNode display Checkbox or not | boolean | - | | | disableCheckbox | Disables the checkbox of the treeNode | boolean | false | | | disabled | Disabled or not | boolean | false | | | isLeaf | Leaf node or not | boolean | false | | | key | Required property (unless using `treeDataSimpleMode`), should be unique in the tree | string | - | | | selectable | Whether can be selected | boolean | true | | | title | Content showed on the treeNodes | ReactNode | `---` | | | value | Will be treated as `treeNodeFilterProp` by default, should be unique in the tree | string | - | | ## Semantic DOM ## Design Token ## FAQ ### How to get parent node in onChange? We don't provide this since performance consideration. You can get by this way: ### Why sometime customize Option cause scroll break? You can ref Select [FAQ](/components/select). ### Why `loadData` not trigger when searching? In earlier version, `loadData` will be triggered when searching. But we got feedback that it will block network when inputting. So we change it to not trigger `loadData` when searching. But you can still handle async logic by `filterTreeNode`: ```tsx { const match = YOUR_LOGIC_HERE; if (match && !treeNode.isLeaf && !treeNode.children) { // Do some loading logic } return match; }} /> ``` ### Why can't popup scroll horizontally? Just turn off virtual scrolling, because the `scrollWidth` of the complete list cannot be accurately measured when virtual scrolling is turned on. --- Title: Tour URL: https://ant.design/components/tour --- ## When To Use Use when you want to guide users through a product. ## Examples Basic Non-modal Placement Custom mask style Custom indicator Custom action Custom highlighted area style \_InternalPanelDoNotUseOrYouWillBeFired ## API Common props ref：[Common props](/docs/react/common-props) ### Tour | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | arrow | Whether to show the arrow, including the configuration whether to point to the center of the element | `boolean`\|`{ pointAtCenter: boolean}` | `true` | | | closeIcon | Customize close icon | `React.ReactNode` | `true` | 5.9.0 | | disabledInteraction | Disable interaction on highlighted area. | `boolean` | `false` | 5.13.0 | | gap | Control the radius of the highlighted area and the offset between highlighted area and the element. | `{ offset?: number \| [number, number]; radius?: number }` | `{ offset?: 6 ; radius?: 2 }` | 5.0.0 (array type `offset`: 5.9.0) | | placement | Position of the guide card relative to the target element | `center` `left` `leftTop` `leftBottom` `right` `rightTop` `rightBottom` `top` `topLeft` `topRight` `bottom` `bottomLeft` `bottomRight` | `bottom` | | | onClose | Callback function on shutdown | `Function` | - | | | mask | Whether to enable masking, change mask style and fill color by pass custom props | `boolean \| { style?: React.CSSProperties; color?: string; }` | `true` | | | type | Type, affects the background color and text color | `default` `primary` | `default` | | | open | Open tour | `boolean` | - | | | onChange | Callback when the step changes. Current is the previous step | `(current: number) => void` | - | | | current | What is the current step | `number` | - | | | scrollIntoViewOptions | support pass custom scrollIntoView options | `boolean \| ScrollIntoViewOptions` | `true` | 5.2.0 | | indicatorsRender | custom indicator | `(current: number, total: number) => ReactNode` | - | 5.2.0 | | actionsRender | custom action | `(originNode: ReactNode, info: { current: number, total: number }) => ReactNode` | - | 5.25.0 | | zIndex | Tour's zIndex | number | 1001 | 5.3.0 | | getPopupContainer | Set the rendering node of Tour floating layer | `(node: HTMLElement) => HTMLElement` | body | 5.12.0 | ### TourStep | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | target | Get the element the guide card points to. Empty makes it show in center of screen | `() => HTMLElement` \| `HTMLElement` | - | | | arrow | Whether to show the arrow, including the configuration whether to point to the center of the element | `boolean` `{ pointAtCenter: boolean}` | `true` | | | closeIcon | Customize close icon | `React.ReactNode` | `true` | 5.9.0 | | cover | Displayed pictures or videos | `ReactNode` | - | | | title | title | `ReactNode` | - | | | description | description | `ReactNode` | - | | | placement | Position of the guide card relative to the target element | `center` `left` `leftTop` `leftBottom` `right` `rightTop` `rightBottom` `top` `topLeft` `topRight` `bottom` `bottomLeft` `bottomRight` | `bottom` | | | onClose | Callback function on shutdown | `Function` | - | | | mask | Whether to enable masking, change mask style and fill color by pass custom props, the default follows the `mask` property of Tour | `boolean \| { style?: React.CSSProperties; color?: string; }` | `true` | | | type | Type, affects the background color and text color | `default` `primary` | `default` | | | nextButtonProps | Properties of the Next button | `{ children: ReactNode; onClick: Function }` | - | | | prevButtonProps | Properties of the previous button | `{ children: ReactNode; onClick: Function }` | - | | | scrollIntoViewOptions | support pass custom scrollIntoView options, the default follows the `scrollIntoViewOptions` property of Tour | `boolean \| ScrollIntoViewOptions` | `true` | 5.2.0 | ## Semantic DOM ## Design Token --- Title: Transfer URL: https://ant.design/components/transfer --- ## When To Use - It is a select control essentially which can be use for selecting multiple items. - Transfer can display more information for items and take up more space. Transfer the elements between two columns in an intuitive and efficient way. One or more elements can be selected from either column, one click on the proper `direction` button, and the transfer is done. The left column is considered the `source` and the right column is considered the `target`. As you can see in the API description, these names are reflected in. > notice: Transfer is a controlled component, uncontrolled mode is not supported. ## Examples Basic One Way Search Advanced Custom datasource Custom Actions Pagination Table Transfer Tree Transfer Status Custom Select All Labels Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | actions | A set of operations that are sorted from top to bottom. When an array of strings is provided, default buttons will be used; when an array of ReactNode is provided, custom elements will be used | ReactNode\[] | \[`>`, `<`] | 6.0.0 | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | | | dataSource | Used for setting the source data. The elements that are part of this array will be present the left column. Except the elements whose keys are included in `targetKeys` prop | [RecordType extends TransferItem = TransferItem](https://github.com/ant-design/ant-design/blob/1bf0bab2a7bc0a774119f501806e3e0e3a6ba283/components/transfer/index.tsx#L12)\[] | \[] | | | disabled | Whether disabled transfer | boolean | false | | | selectionsIcon | custom dropdown icon | React.ReactNode | | 5.8.0 | | filterOption | A function to determine whether an item should show in search result list, only works when searching, (add `direction` support since 5.9.0+) | (inputValue, option, direction: `left` \| `right`): boolean | - | | | footer | A function used for rendering the footer | (props, { direction }) => ReactNode | - | direction: 4.17.0 | | ~~listStyle~~ | A custom CSS style used for rendering the transfer columns. Use `styles.section` instead | object \| ({direction: `left` \| `right`}) => object | - | | | locale | The i18n text including filter, empty text, item unit, etc | { itemUnit: string; itemsUnit: string; searchPlaceholder: string; notFoundContent: ReactNode \| ReactNode[]; } | { itemUnit: `item`, itemsUnit: `items`, notFoundContent: `The list is empty`, searchPlaceholder: `Search here` } | | | oneWay | Display as single direction style | boolean | false | 4.3.0 | | ~~operations~~ | A set of operations that are sorted from top to bottom. Use `actions` instead. | string\[] | \[`>`, `<`] | | | ~~operationStyle~~ | A custom CSS style used for rendering the operations column. Use `styles.actions` instead. | object | - | | | pagination | Use pagination. Not work in render props | boolean \| { pageSize: number, simple: boolean, showSizeChanger?: boolean, showLessItems?: boolean } | false | 4.3.0 | | render | The function to generate the item shown on a column. Based on an record (element of the dataSource array), this function should return a React element which is generated from that record. Also, it can return a plain object with `value` and `label`, `label` is a React element and `value` is for title | (record) => ReactNode | - | | | selectAllLabels | A set of customized labels for select all checkboxes on the header | (ReactNode \| (info: { selectedCount: number, totalCount: number }) => ReactNode)\[] | - | | | selectedKeys | A set of keys of selected items | string\[] \| number\[] | \[] | | | showSearch | If included, a search box is shown on each column | boolean \| { placeholder:string,defaultValue:string } | false | | | showSelectAll | Show select all checkbox on the header | boolean | true | | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | styles | Semantic DOM style | [Record](#semantic-dom) | - | | | targetKeys | A set of keys of elements that are listed on the right column | string\[] \| number\[] | \[] | | | titles | A set of titles that are sorted from left to right | ReactNode\[] | - | | | onChange | A callback function that is executed when the transfer between columns is complete | (targetKeys, direction, moveKeys): void | - | | | onScroll | A callback function which is executed when scroll options list | (direction, event): void | - | | | onSearch | A callback function which is executed when search field are changed | (direction: `left` \| `right`, value: string): void | - | | | onSelectChange | A callback function which is executed when selected items are changed | (sourceSelectedKeys, targetSelectedKeys): void | - | | ### Render Props Transfer accept `children` to customize render list, using follow props: | Property | Description | Type | Version | | --- | --- | --- | --- | | direction | List render direction | `left` \| `right` | | | disabled | Disable list or not | boolean | | | filteredItems | Filtered items | RecordType\[] | | | selectedKeys | Selected items | string\[] \| number\[] | | | onItemSelect | Select item | (key: string \| number, selected: boolean) | | | onItemSelectAll | Select a group of items | (keys: string\[] \| number\[], selected: boolean) | | #### example ```jsx {(listProps) => } ``` ## Warning According the [standard](https://react.dev/learn/rendering-lists#why-does-react-need-keys) of React, the key should always be supplied directly to the elements in the array. In Transfer, the keys should be set on the elements included in `dataSource` array. By default, `key` property is used as an unique identifier. If there's no `key` in your data, you should use `rowKey` to specify the key that will be used for uniquely identify each element. ```jsx // eg. your primary key is `uid` return record.uid} />; ``` ## Semantic DOM ## Design Token ## FAQ ### How to support fetch and present data from a remote server in Transfer column. In order to keep the page number synchronized, you can disable columns you checked without removing the option: --- Title: Tree URL: https://ant.design/components/tree --- ## When To Use Almost anything can be represented in a tree structure. Examples include directories, organization hierarchies, biological classifications, countries, etc. The `Tree` component is a way of representing the hierarchical relationship between these things. You can also expand, collapse, and select a treeNode within a `Tree`. ## Examples Basic Controlled Tree draggable load data asynchronously Searchable Tree with line Customize Icon directory Directory Debug Customize collapse/expand icon Virtual scroll Drag Debug Big data Block Node Component Token Multiple lines ## API Common props ref：[Common props](/docs/react/common-props) ### Tree props | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowDrop | Whether to allow dropping on the node | ({ dropNode, dropPosition }) => boolean | - | | | autoExpandParent | Whether to automatically expand a parent treeNode | boolean | false | | | blockNode | Whether treeNode fill remaining horizontal space | boolean | false | | | checkable | Add a Checkbox before the treeNodes | boolean | false | | | checkedKeys | (Controlled) Specifies the keys of the checked treeNodes (PS: When this specifies the key of a treeNode which is also a parent treeNode, all the children treeNodes of will be checked; and vice versa, when it specifies the key of a treeNode which is a child treeNode, its parent treeNode will also be checked. When `checkable` and `checkStrictly` is true, its object has `checked` and `halfChecked` property. Regardless of whether the child or parent treeNode is checked, they won't impact each other | string\[] \| {checked: string\[], halfChecked: string\[]} | \[] | | | checkStrictly | Check treeNode precisely; parent treeNode and children treeNodes are not associated | boolean | false | | | className | Additional class to Tree | string | - | | | defaultCheckedKeys | Specifies the keys of the default checked treeNodes | string\[] | \[] | | | defaultExpandAll | Whether to expand all treeNodes by default | boolean | false | | | defaultExpandedKeys | Specify the keys of the default expanded treeNodes | string\[] | \[] | | | defaultExpandParent | If auto expand parent treeNodes when init | boolean | true | | | defaultSelectedKeys | Specifies the keys of the default selected treeNodes | string\[] | \[] | | | disabled | Whether the tree is disabled | boolean | false | | | draggable | Specifies whether this Tree or the node is draggable. Use `icon: false` to disable drag handler icon | boolean \| ((node: DataNode) => boolean) \| { icon?: React.ReactNode \| false, nodeDraggable?: (node: DataNode) => boolean } | false | `config`: 4.17.0 | | expandedKeys | (Controlled) Specifies the keys of the expanded treeNodes | string\[] | \[] | | | fieldNames | Customize node title, key, children field name | object | { title: `title`, key: `key`, children: `children` } | 4.17.0 | | filterTreeNode | Defines a function to filter (highlight) treeNodes. When the function returns `true`, the corresponding treeNode will be highlighted | function(node) | - | | | height | Config virtual scroll height. Will not support horizontal scroll when enabled | number | - | | | icon | Insert a custom icon before the title. Need to set `showIcon` to true | ReactNode \| (props) => ReactNode | - | | | loadData | Load data asynchronously | function(node) | - | | | loadedKeys | (Controlled) Set loaded tree nodes. Need to work with `loadData` | string\[] | \[] | | | motion | Custom motion config for the tree | CSSMotionProps | - | | | multiple | Allows selecting multiple treeNodes | boolean | false | | | rootStyle | Style on the root element | CSSProperties | - | 4.20.0 | | selectable | Whether it can be selected | boolean | true | | | selectedKeys | (Controlled) Specifies the keys of the selected treeNodes, multiple selection needs to set `multiple` to true | string\[] | - | | | showIcon | Controls whether to display the `icon` node (no default style) | boolean | false | | | showLine | Shows a connecting line | boolean \| {showLeafIcon: ReactNode \| ((props: AntTreeNodeProps) => ReactNode)} | false | | | style | Style of Tree component | CSSProperties | - | | | switcherIcon | Customize expand/collapse icons for tree nodes (With default rotate angular style) | ReactNode \| ((props: AntTreeNodeProps) => ReactNode) | - | renderProps: 4.20.0 | | switcherLoadingIcon | Customize loading icons for tree nodes | ReactNode | - | 5.20.0 | | titleRender | Customize tree node title render | (nodeData) => ReactNode | - | 4.5.0 | | treeData | The treeNodes data Array, if set it then you need not to construct children TreeNode. (key should be unique across the whole array) | array<{ key, title, children, \[disabled, selectable] }> | - | | | virtual | Disable virtual scroll when set to false | boolean | true | 4.1.0 | | onCheck | Callback function for when the onCheck event occurs | function(checkedKeys, e:{checked: boolean, checkedNodes, node, event, halfCheckedKeys}) | - | | | onDragEnd | Callback function for when the onDragEnd event occurs | function({event, node}) | - | | | onDragEnter | Callback function for when the onDragEnter event occurs | function({event, node, expandedKeys}) | - | | | onDragLeave | Callback function for when the onDragLeave event occurs | function({event, node}) | - | | | onDragOver | Callback function for when the onDragOver event occurs | function({event, node}) | - | | | onDragStart | Callback function for when the onDragStart event occurs | function({event, node}) | - | | | onDrop | Callback function for when the onDrop event occurs | function({event, node, dragNode, dragNodesKeys}) | - | | | onExpand | Callback function for when a treeNode is expanded or collapsed | function(expandedKeys, {expanded: boolean, node}) | - | | | onLoad | Callback function for when a treeNode is loaded | function(loadedKeys, {event, node}) | - | | | onRightClick | Callback function for when the user right clicks a treeNode | function({event, node}) | - | | | onSelect | Callback function for when the user clicks a treeNode | function(selectedKeys, e:{selected: boolean, selectedNodes, node, event}) | - | | ### TreeNode props | Property | Description | Type | Default | | | --- | --- | --- | --- | --- | | checkable | When Tree is checkable, set TreeNode display Checkbox or not | boolean | - | | | disableCheckbox | Disables the checkbox of the treeNode | boolean | false | | | disabled | Disables the treeNode | boolean | false | | | icon | Customize icon. When you pass component, whose render will receive full TreeNode props as component props | ReactNode \| (props) => ReactNode | - | | | isLeaf | Determines if this is a leaf node (effective when `loadData` is specified). `false` will force the TreeNode to be treated as a parent node | boolean | - | | | key | Used with (default)ExpandedKeys / (default)CheckedKeys / (default)SelectedKeys. P.S.: It must be unique in all of treeNodes of the tree | string | (internal calculated position of treeNode) | | | selectable | Set whether the treeNode can be selected | boolean | true | | | title | Title | ReactNode | `---` | | ### DirectoryTree props | Property | Description | Type | Default | | --- | --- | --- | --- | | expandAction | Directory opening logic, options: false \| `click` \| `doubleClick` | string \| boolean | `click` | ## Note Before `3.4.0`: The number of treeNodes can be very large, but when `checkable=true`, it will increase the compute time. So, we cache some calculations (e.g. `this.treeNodesStates`) to avoid double computing. But, this brings some restrictions. **When you load treeNodes asynchronously, you should render tree like this**: ```jsx { this.state.treeData.length ? ( {this.state.treeData.map((data) => ( ))} ) : ( 'loading tree' ); } ``` ### Tree Methods | Name | Description | | --- | --- | | scrollTo({ key: string \| number; align?: 'top' \| 'bottom' \| 'auto'; offset?: number }) | Scroll to key item in virtual scroll | ## Semantic DOM ## Design Token ## FAQ ### Why defaultExpandAll not working on ajax data? `default` prefix props only work when initializing. So `defaultExpandAll` has already been executed when ajax loads data. You can control `expandedKeys` or render the Tree when data is loaded to realize expanding all nodes. ### Virtual scroll limitation Virtual scroll only render items in visible region. Thus not support auto width (like long `title` with horizontal scroll). ### What does `disabled` node work logic in the tree? Tree change its data by conduction. Includes checked or auto expanded, it will conduction state to parent / children node until current node is `disabled`. So if a controlled node is `disabled`, it will only modify self state and not affect other nodes. For example, a parent node contains 3 child nodes and one of them is `disabled`. When check the parent node, it will only check rest 2 child nodes. As the same, when check these 2 child node, parent will be checked whatever checked state the `disabled` one is. This conduction logic prevents modifying `disabled` parent checked state by checking children nodes, and users cannot modify directly with click which avoids interactive conflicts. If you want to modify this conduction logic, you can customize it with the `checkStrictly` prop. --- Title: Tag URL: https://ant.design/components/tag --- ## When To Use - It can be used to tag by dimension or property. - When categorizing. ## Examples Basic Colorful Tag Add & Remove Dynamically Checkable Animate Icon Status Tag Customize close Draggable Tag Component Token Disabled ## API Common props ref：[Common props](/docs/react/common-props) ### Tag | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | | | closeIcon | Custom close icon. 5.7.0: close button will be hidden when setting to `null` or `false` | ReactNode | false | 4.4.0 | | color | Color of the Tag | string | - | | | variant | Variant of the tag | `'filled' \| 'solid' \| 'outlined'` | `'filled'` | 6.0.0 | | icon | Set the icon of tag | ReactNode | - | | | disabled | Whether the tag is disabled | boolean | false | 6.0.0 | | href | The address to jump when clicking, when this property is specified, the `tag` component will be rendered as an `` tag | string | - | 6.0.0 | | styles | Semantic DOM style | [Record](#semantic-dom) | - | | | target | The target attribute of the a tag, which takes effect when href is specified | string | - | 6.0.0 | | onClose | Callback executed when tag is closed | (e: React.MouseEvent) => void | - | | ### Tag.CheckableTag | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | checked | Checked status of Tag | boolean | false | | | icon | Set the icon of tag | ReactNode | - | 5.27.0 | | onChange | Callback executed when Tag is checked/unchecked | (checked) => void | - | | ### Tag.CheckableTagGroup | 参数 | 说明 | 类型 | 默认值 | 版本 | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | | | defaultValue | Initial value | `string \| number \| Array \| null` | - | | | disabled | Disable check/uncheck | `boolean` | - | | | multiple | Multiple select mode | `boolean` | - | | | styles | Semantic DOM style | [Record](#semantic-dom) | - | | | value | Value of checked tag(s) | `string \| number \| Array \| null` | - | | | options | Option list | `Array<{ label: ReactNode; value: string \| number } \| string \| number>` | - | | | onChange | Callback when Tag is checked/unchecked | `(value: string \| number \| Array \| null) => void` | - | | ## Semantic DOM ### Tag ### Tag.CheckableTagGroup ## Design Token --- Title: TimePicker URL: https://ant.design/components/time-picker --- ## When To Use By clicking the input box, you can select a time from a popup panel. ## Examples Basic Under Control Three Sizes Need Confirm disabled Hour and minute interval option Addon 12 hours Change on scroll Colored Popup Time Range Picker Variants Status Prefix and Suffix _InternalPanelDoNotUseOrYouWillBeFired ## API --- Common props ref：[Common props](/docs/react/common-props) ```jsx import dayjs from 'dayjs'; import customParseFormat from 'dayjs/plugin/customParseFormat' dayjs.extend(customParseFormat) ; ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Customize clear icon | boolean \| { clearIcon?: ReactNode } | true | 5.8.0: Support object type | | autoFocus | If get focus when component mounted | boolean | false | | | cellRender | Custom rendering function for picker cells | (current: number, info: { originNode: React.ReactElement, today: dayjs, range?: 'start' \| 'end', subType: 'hour' \| 'minute' \| 'second' \| 'meridiem' }) => React.ReactNode | - | 5.4.0 | | changeOnScroll | Trigger selection when scroll the column | boolean | false | 5.14.0 | | className | The className of picker | string | - | | | defaultValue | To set default time | [dayjs](http://day.js.org/) | - | | | disabled | Determine whether the TimePicker is disabled | boolean | false | | | disabledTime | To specify the time that cannot be selected | [DisabledTime](#disabledtime) | - | 4.19.0 | | format | To set the time format | string | `HH:mm:ss` | | | getPopupContainer | To set the container of the floating layer, while the default is to create a div element in body | function(trigger) | - | | | hideDisabledOptions | Whether hide the options that can not be selected | boolean | false | | | hourStep | Interval between hours in picker | number | 1 | | | inputReadOnly | Set the `readonly` attribute of the input tag (avoids virtual keyboard on touch devices) | boolean | false | | | minuteStep | Interval between minutes in picker | number | 1 | | | needConfirm | Need click confirm button to trigger value change | boolean | - | 5.14.0 | | open | Whether to popup panel | boolean | false | | | placeholder | Display when there's no value | string \| \[string, string] | `Select a time` | | | placement | The position where the selection box pops up | `bottomLeft` `bottomRight` `topLeft` `topRight` | bottomLeft | | | ~~popupClassName~~ | The className of panel, please use `classNames.popup` instead | string | - | | | ~~popupStyle~~ | The style of panel, please use `styles.popup` instead | CSSProperties | - | | | prefix | The custom prefix | ReactNode | - | 5.22.0 | | renderExtraFooter | Called from time picker panel to render some addon to its bottom | () => ReactNode | - | | | secondStep | Interval between seconds in picker | number | 1 | | | showNow | Whether to show `Now` button on panel | boolean | - | 4.4.0 | | size | To determine the size of the input box, the height of `large` and `small`, are 40px and 24px respectively, while default size is 32px | `large` \| `middle` \| `small` | - | | | status | Set validation status | 'error' \| 'warning' \| 'success' \| 'validating' | - | 4.19.0 | | suffixIcon | The custom suffix icon | ReactNode | - | | | use12Hours | Display as 12 hours format, with default format `h:mm:ss a` | boolean | false | | | value | To set time | [dayjs](http://day.js.org/) | - | | | variant | Variants of picker | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | onCalendarChange | Callback function, can be executed when the start time or the end time of the range is changing. `info` argument is added in 4.4.0 | function(dates: \[dayjs, dayjs], dateStrings: \[string, string], info: { range:`start`\|`end` }) | - | | | onChange | A callback function, can be executed when the selected time is changing | function(time: dayjs, timeString: string): void | - | | | onOpenChange | A callback function which will be called while panel opening/closing | (open: boolean) => void | - | | #### DisabledTime ```typescript type DisabledTime = (now: Dayjs) => { disabledHours?: () => number[]; disabledMinutes?: (selectedHour: number) => number[]; disabledSeconds?: (selectedHour: number, selectedMinute: number) => number[]; disabledMilliseconds?: ( selectedHour: number, selectedMinute: number, selectedSecond: number, ) => number[]; }; ``` Note: `disabledMilliseconds` is added in `5.14.0`. ## Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ### RangePicker Same props from [RangePicker](/components/date-picker/#rangepicker) of DatePicker. And includes additional props: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | disabledTime | To specify the time that cannot be selected | [RangeDisabledTime](#rangedisabledtime) | - | 4.19.0 | | order | Order start and end time | boolean | true | 4.1.0 | ### RangeDisabledTime ```typescript type RangeDisabledTime = ( now: Dayjs, type = 'start' | 'end', ) => { disabledHours?: () => number[]; disabledMinutes?: (selectedHour: number) => number[]; disabledSeconds?: (selectedHour: number, selectedMinute: number) => number[]; }; ``` ## Semantic DOM ## Design Token ## FAQ - [How to use TimePicker with customize date library like dayjs](/docs/react/use-custom-date-library#timepicker) --- Title: Tooltip URL: https://ant.design/components/tooltip --- ## When To Use - The tip is shown on mouse enter, and is hidden on mouse leave. The Tooltip doesn't support complex text or operations. - To provide an explanation of a `button/text/operation`. It's often used instead of the html `title` attribute. ## Examples Basic Placement Arrow Auto Shift Adjust placement automatically Destroy tooltip when hidden Colorful Tooltip _InternalPanelDoNotUseOrYouWillBeFired Debug Disabled Disabled children Wrap custom component ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | | -------- | ----------------------------- | ---------------------------- | ------- | | title | The text shown in the tooltip | ReactNode \| () => ReactNode | - | ### Common API ## Semantic DOM ## Design Token ## FAQ ### Why Tooltip not update content when close? Tooltip will cache content when it is closed to avoid flicker when content is updated: ```jsx // `title` will not blink when `user` is empty ```
    no blink
    If need update content when close, you can set `fresh` property ([#44830](https://github.com/ant-design/ant-design/issues/44830)): ```jsx ```
    no blink
    --- --- Title: Switch URL: https://ant.design/components/switch --- ## When To Use - If you need to represent the switching between two states or on-off state. - The difference between `Switch` and `Checkbox` is that `Switch` will trigger a state change directly when you toggle it, while `Checkbox` is generally used for state marking, which should work in conjunction with submit operation. ## Examples Basic Disabled Text & icon Two sizes Loading Custom component token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoFocus | Whether get focus when component mounted | boolean | false | | | checked | Determine whether the Switch is checked | boolean | false | | | checkedChildren | The content to be shown when the state is checked | ReactNode | - | | | className | The additional class to Switch | string | - | | | defaultChecked | Whether to set the initial state | boolean | false | | | defaultValue | Alias for `defaultChecked` | boolean | - | 5.12.0 | | disabled | Disable switch | boolean | false | | | loading | Loading state of switch | boolean | false | | | size | The size of the Switch, options: `default` `small` | string | `default` | | | unCheckedChildren | The content to be shown when the state is unchecked | ReactNode | - | | | value | Alias for `checked` | boolean | - | 5.12.0 | | onChange | Trigger when the checked state is changing | function(checked: boolean, event: Event) | - | | | onClick | Trigger when clicked | function(checked: boolean, event: Event) | - | | ## Methods | Name | Description | | ------- | ------------ | | blur() | Remove focus | | focus() | Get focus | ## Semantic DOM ## Design Token ## FAQ ### Why not work in Form.Item? Form.Item default bind value to `value` property, but Switch value property is `checked`. You can use `valuePropName` to change bind property. ```tsx | pure ``` --- Title: Timeline URL: https://ant.design/components/timeline --- ## When To Use - When a series of information needs to be ordered by time (ascending or descending). - When you need a timeline to make a visual connection. ## Examples Basic Variant Loading and Reversing Pending and Reversing Alternate Horizontal Horizontal Custom End alternate Title Title Offset Semantic Sample Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Timeline | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | items | Each node of timeline | [Items](#Items)[] | - | | | mode | By sending `alternate` the timeline will distribute the nodes to the left and right | `start` \| `alternate` \| `end` | `start` | | | orientation | Set the direction of the timeline | `vertical` \| `horizontal` | `vertical` | | | ~~pending~~ | Set the last ghost node's existence or its content. Use `item.loading` instead | ReactNode | false | | | ~~pendingDot~~ | Set the dot of the last ghost node when pending is true. Use `item.icon` instead | ReactNode | <LoadingOutlined /> | | | reverse | Whether reverse nodes or not | boolean | false | | | titleSpan | Set the title span space. It is the distance to the center of the dot | number \| string | 12 | | | variant | Config style variant | `filled` \| `outlined` | `outlined` | | ### Items Node of timeline. | Property | Description | Type | Default | | --- | --- | --- | --- | | color | Set the circle's color to `blue`, `red`, `green`, `gray` or other custom colors | string | `blue` | | content | Set the content | ReactNode | - | | ~~children~~ | Set the content. Please use `content` instead | ReactNode | - | | ~~dot~~ | Customize timeline dot. Please use `icon` instead | ReactNode | - | | icon | Customize node icon | ReactNode | - | | ~~label~~ | Set the label. Please use `title` instead | ReactNode | - | | loading | Set loading state | boolean | false | | placement | Customize node placement | `start` \| `end` | - | | ~~position~~ | Customize node position，Please use `placement` instead | `start` \| `end` | - | | title | Set the title | ReactNode | - | ## Semantic DOM ### Timeline ### Timeline Items ## Design Token --- Title: Statistic URL: https://ant.design/components/statistic --- ## When To Use - When want to highlight some data. - When want to display statistic data with description. ## Examples Basic Unit Animated number In Card Timer Component Token ## API Common props ref：[Common props](/docs/react/common-props) #### Statistic | Property | Description | Type | Default | Version | | ---------------- | ----------------------------- | -------------------- | ------- | ------- | | decimalSeparator | The decimal separator | string | `.` | | | formatter | Customize value display logic | (value) => ReactNode | - | | | groupSeparator | Group separator | string | `,` | | | loading | Loading status of Statistic | boolean | false | 4.8.0 | | precision | The precision of input value | number | - | | | prefix | The prefix node of value | ReactNode | - | | | suffix | The suffix node of value | ReactNode | - | | | title | Display title | ReactNode | - | | | value | Display value | string \| number | - | | | valueStyle | Set value section style | CSSProperties | - | | #### Statistic.Countdown Deprecated | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | format | Format as [dayjs](https://day.js.org/) | string | `HH:mm:ss` | | | prefix | The prefix node of value | ReactNode | - | | | suffix | The suffix node of value | ReactNode | - | | | title | Display title | ReactNode | - | | | value | Set target countdown time | number | - | | | valueStyle | Set value section style | CSSProperties | - | | | onFinish | Trigger when time's up | () => void | - | | | onChange | Trigger when time's changing | (value: number) => void | - | 4.16.0 | #### Statistic.Timer 5.25.0+ | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | type | time counter down or up | `countdown` `countup` | - | | | format | Format as [dayjs](https://day.js.org/) | string | `HH:mm:ss` | | | prefix | The prefix node of value | ReactNode | - | | | suffix | The suffix node of value | ReactNode | - | | | title | Display title | ReactNode | - | | | value | Set target countdown time | number | - | | | valueStyle | Set value section style | CSSProperties | - | | | onFinish | Trigger when time's up, only to be called when type is `countdown` | () => void | - | | | onChange | Trigger when time's changing | (value: number) => void | - | | ## Semantic DOM ## Design Token --- Title: Tabs URL: https://ant.design/components/tabs --- ### When To Use Ant Design has 3 types of Tabs for different situations. - Card Tabs: for managing too many closeable views. - Normal Tabs: for functional aspects of a page. - [Radio.Button](/components/radio/#radio-demo-radiobutton): for secondary tabs. ## Examples Basic Disabled Centered Icon Indicator Slide Extra content Size Placement Card type tab Add & close tab Container of card type Tab Customized trigger of new tab Customized bar of tab Draggable Tabs Animated Nest component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Tabs | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | activeKey | Current TabPane's key | string | - | | | addIcon | Customize add icon, only works with `type="editable-card"` | ReactNode | `` | 4.4.0 | | animated | Whether to change tabs with animation. | boolean \| { inkBar: boolean, tabPane: boolean } | { inkBar: true, tabPane: false } | | | centered | Centers tabs | boolean | false | 4.4.0 | | defaultActiveKey | Initial active TabPane's key, if `activeKey` is not set | string | `The key of first tab` | | | hideAdd | Hide plus icon or not. Only works while `type="editable-card"` | boolean | false | | | indicator | Customize `size` and `align` of indicator | { size?: number \| (origin: number) => number; align: `start` \| `center` \| `end`; } | - | 5.13.0 | | items | Configure tab content | [TabItemType](#tabitemtype) | [] | 4.23.0 | | more | Customize the collapse menu | [MoreProps](#moreprops) | { icon: `` , trigger: 'hover' } | | | removeIcon | The custom icon of remove, only works with `type="editable-card"` | ReactNode | `` | 5.15.0 | | ~~popupClassName~~ | `className` for more dropdown, please use `classNames.popup` instead | string | - | 4.21.0 | | renderTabBar | Replace the TabBar | (props: DefaultTabBarProps, DefaultTabBar: React.ComponentClass) => React.ReactElement | - | | | size | Preset tab bar size | `large` \| `middle` \| `small` | `middle` | | | tabBarExtraContent | Extra content in tab bar | ReactNode \| {left?: ReactNode, right?: ReactNode} | - | object: 4.6.0 | | tabBarGutter | The gap between tabs | number | - | | | tabBarStyle | Tab bar style object | CSSProperties | - | | | tabPlacement | Placement of tabs | `top` \| `end` \| `bottom` \| `start` | `top` | | | ~~tabPosition~~ | Position of tabs | `top` \| `right` \| `bottom` \| `left`, please use `tabPlacement` instead | `top` | | | ~~destroyInactiveTabPane~~ | Whether destroy inactive TabPane when change tab, use `destroyOnHidden` instead | boolean | false | | | destroyOnHidden | Whether destroy inactive TabPane when change tab | boolean | false | 5.25.0 | | type | Basic style of tabs | `line` \| `card` \| `editable-card` | `line` | | | onChange | Callback executed when active tab is changed | (activeKey: string) => void | - | | | onEdit | Callback executed when tab is added or removed. Only works while `type="editable-card"` | (action === 'add' ? event : targetKey, action) => void | - | | | onTabClick | Callback executed when tab is clicked | (key: string, event: MouseEvent) => void | - | | | onTabScroll | Trigger when tab scroll | ({ direction: `left` \| `right` \| `top` \| `bottom` }) => void | - | 4.3.0 | More option at [@rc-component/tabs](https://github.com/react-component/tabs#tabs) ### TabItemType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | closeIcon | Customize close icon in TabPane's head. Only works while `type="editable-card"`. 5.7.0: close button will be hidden when setting to `null` or `false` | ReactNode | - | | | ~~destroyInactiveTabPane~~ | Whether destroy inactive TabPane when change tab, use `destroyOnHidden` instead | boolean | false | 5.11.0 | | destroyOnHidden | Whether destroy inactive TabPane when change tab | boolean | false | 5.25.0 | | disabled | Set TabPane disabled | boolean | false | | | forceRender | Forced render of content in tabs, not lazy render after clicking on tabs | boolean | false | | | key | TabPane's key | string | - | | | label | TabPane's head display text | ReactNode | - | | | icon | TabPane's head display icon | ReactNode | - | 5.12.0 | | children | TabPane's head display content | ReactNode | - | | | closable | Whether a close (x) button is visible, Only works while `type="editable-card"` | boolean | true | | ### MoreProps | Property | Description | Type | Default | Version | | ----------------------------------------- | --------------- | --------- | ------- | ------- | | icon | The custom icon | ReactNode | - | | | [DropdownProps](/components/dropdown#api) | | | | | ## Semantic DOM ## Design Token --- Title: Table URL: https://ant.design/components/table --- ## When To Use - To display a collection of structured data. - To sort, search, paginate, filter data. ## How To Use Specify `dataSource` of Table as an array of data. ```jsx const dataSource = [ { key: '1', name: 'Mike', age: 32, address: '10 Downing Street', }, { key: '2', name: 'John', age: 42, address: '10 Downing Street', }, ]; const columns = [ { title: 'Name', dataIndex: 'name', key: 'name', }, { title: 'Age', dataIndex: 'age', key: 'age', }, { title: 'Address', dataIndex: 'address', key: 'address', }, ];
    ; ``` ## Promotion - [Kitchen Sketch Plugin 💎](https://kitchen.alipay.com) - [ProTable - Advanced Tables](https://procomponents.ant.design/en-US/components/table) - [S2 - Analytical Tables](https://github.com/antvis/s2/) ## Examples Basic Usage JSX style API selection Selection and operation Custom selection Selection Perf Filter and sorter Filter in Tree Filter search Multiple sorter Reset filters and sorters Customized filter panel Ajax size size border, title and footer Expandable Row Customizable expansion position Order Specific Column colSpan and rowSpan Tree data Tree data ellipsis debug demo Fixed Header Fixed Columns Stack Fixed Columns Fixed Columns and Header Hidden Columns Grouping table head Editable Cells Editable Rows Nested tables Drag sorting Drag Column sorting Drag sorting with handler Resizable column ellipsis column ellipsis column custom tooltip Custom empty Summary Virtual list Responsive Nested Bordered Table Debug Pagination Settings Custom selection group Fixed header and scroll bar with the page Dynamic Settings selections with icon Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Table | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | bordered | Whether to show all table borders | boolean | false | | | columns | Columns of table | [ColumnsType](#column)\[] | - | | | components | Override default table elements | [TableComponents](https://github.com/react-component/table/blob/75ee0064e54a4b3215694505870c9d6c817e9e4a/src/interface.ts#L129) | - | | | dataSource | Data record array to be displayed | object\[] | - | | | expandable | Config expandable content | [expandable](#expandable) | - | | | footer | Table footer renderer | function(currentPageData) | - | | | getPopupContainer | The render container of dropdowns in table | (triggerNode) => HTMLElement | () => TableHtmlElement | | | loading | Loading status of table | boolean \| [Spin Props](/components/spin/#api) | false | | | locale | The i18n text including filter, sort, empty text, etc | object | [Default Value](https://github.com/ant-design/ant-design/blob/6dae4a7e18ad1ba193aedd5ab6867e1d823e2aa4/components/locale/en_US.tsx#L19-L37) | | | pagination | Config of pagination. You can ref table pagination [config](#pagination) or full [`pagination`](/components/pagination/) document, hide it by setting it to `false` | object \| `false` | - | | | rowClassName | Row's className | function(record, index): string | - | | | rowKey | Row's unique key, could be a string or function that returns a string | string \| function(record): string | `key` | | | rowSelection | Row selection [config](#rowselection) | object | - | | | rowHoverable | Row hover | boolean | true | 5.16.0 | | scroll | Whether the table can be scrollable, [config](#scroll) | object | - | | | showHeader | Whether to show table header | boolean | true | | | showSorterTooltip | The header show next sorter direction tooltip. It will be set as the property of Tooltip if its type is object | boolean \| [Tooltip props](/components/tooltip/#api) & `{target?: 'full-header' \| 'sorter-icon' }` | { target: 'full-header' } | 5.16.0 | | size | Size of table | `large` \| `middle` \| `small` | `large` | | | sortDirections | Supported sort way, could be `ascend`, `descend` | Array | \[`ascend`, `descend`] | | | sticky | Set sticky header and scroll bar | boolean \| `{offsetHeader?: number, offsetScroll?: number, getContainer?: () => HTMLElement}` | - | 4.6.0 (getContainer: 4.7.0) | | summary | Summary content | (currentData) => ReactNode | - | | | tableLayout | The [table-layout](https://developer.mozilla.org/en-US/docs/Web/CSS/table-layout) attribute of table element | - \| `auto` \| `fixed` | -
    `fixed` when header/columns are fixed, or using `column.ellipsis` | | | title | Table title renderer | function(currentPageData) | - | | | virtual | Support virtual list | boolean | - | 5.9.0 | | onChange | Callback executed when pagination, filters or sorter is changed | function(pagination, filters, sorter, extra: { currentDataSource: \[], action: `paginate` \| `sort` \| `filter` }) | - | | | onHeaderRow | Set props on per header row | function(columns, index) | - | | | onRow | Set props on per row | function(record, index) | - | | | onScroll | Triggered when the table body is scrolled. Note that only vertical scrolling will trigger the event when `virtual` | function(event) | - | 5.16.0 | ### Table ref | Property | Description | Type | Version | | --- | --- | --- | --- | | nativeElement | The wrap element | HTMLDivElement | 5.11.0 | | scrollTo | Trigger to scroll to target position. `key` match with record `rowKey`. When `offset` is specified, the table will scroll to align the target row to the top with the given offset and not working with `top` | (config: { index?: number, key?: React.Key, top?: number, offset?: number }) => void | 5.11.0 | #### onRow usage Same as `onRow` `onHeaderRow` `onCell` `onHeaderCell` ```jsx
    { return { onClick: (event) => {}, // click row onDoubleClick: (event) => {}, // double click row onContextMenu: (event) => {}, // right button click row onMouseEnter: (event) => {}, // mouse enter row onMouseLeave: (event) => {}, // mouse leave row }; }} onHeaderRow={(columns, index) => { return { onClick: () => {}, // click header row }; }} /> ``` ### Column One of the Table `columns` prop for describing the table's columns, Column has the same API. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | align | The specify which way that column is aligned | `left` \| `right` \| `center` | `left` | | | className | The className of this column | string | - | | | colSpan | Span of this column's title | number | - | | | dataIndex | Display field of the data record, support nest path by string array | string \| string\[] | - | | | defaultFilteredValue | Default filtered values | string\[] | - | | | filterResetToDefaultFilteredValue | click the reset button, whether to restore the default filter | boolean | false | | | defaultSortOrder | Default order of sorted values | `ascend` \| `descend` | - | | | ellipsis | The ellipsis cell content, not working with sorter and filters for now.
    tableLayout would be `fixed` when `ellipsis` is `true` or `{ showTitle?: boolean }` | boolean \| {showTitle?: boolean } | false | showTitle: 4.3.0 | | filterDropdown | Customized filter overlay | ReactNode \| (props: [FilterDropdownProps](https://github.com/ant-design/ant-design/blob/ecc54dda839619e921c0ace530408871f0281c2a/components/table/interface.tsx#L79)) => ReactNode | - | | | filtered | Whether the `dataSource` is filtered | boolean | false | | | filteredValue | Controlled filtered value, filter icon will highlight | string\[] | - | | | filterIcon | Customized filter icon | ReactNode \| (filtered: boolean) => ReactNode | - | | | filterOnClose | Whether to trigger filter when the filter menu closes | boolean | true | 5.15.0 | | filterMultiple | Whether multiple filters can be selected | boolean | true | | | filterMode | To specify the filter interface | 'menu' \| 'tree' | 'menu' | 4.17.0 | | filterSearch | Whether to be searchable for filter menu | boolean \| function(input, record):boolean | false | boolean:4.17.0 function:4.19.0 | | filters | Filter menu config | object\[] | - | | | filterDropdownProps | Customized dropdown props, `filterDropdownOpen` and `onFilterDropdownOpenChange` were available before `<5.22.0` | [DropdownProps](/components/dropdown#api) | - | 5.22.0 | | fixed | (IE not support) Set column to be fixed: `true`(same as `'start'`) `'start'` `'end'` | boolean \| string | false | | | key | Unique key of this column, you can ignore this prop if you've set a unique `dataIndex` | string | - | | | render | Renderer of the table cell. `value` is the value of current cell; `record` is the value object of current row; `index` is the row number. The return value should be a ReactNode | function(value, record, index) {} | - | | | responsive | The list of breakpoints at which to display this column. Always visible if not set | [Breakpoint](https://github.com/ant-design/ant-design/blob/015109b42b85c63146371b4e32b883cf97b088e8/components/_util/responsiveObserve.ts#L1)\[] | - | 4.2.0 | | rowScope | Set scope attribute for all cells in this column | `row` \| `rowgroup` | - | 5.1.0 | | shouldCellUpdate | Control cell render logic | (record, prevRecord) => boolean | - | 4.3.0 | | showSorterTooltip | If header show next sorter direction tooltip, override `showSorterTooltip` in table | boolean \| [Tooltip props](/components/tooltip/) & `{target?: 'full-header' \| 'sorter-icon' }` | { target: 'full-header' } | 5.16.0 | | sortDirections | Supported sort way, override `sortDirections` in `Table`, could be `ascend`, `descend` | Array | \[`ascend`, `descend`] | | | sorter | Sort function for local sort, see [Array.sort](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort)'s compareFunction. If it is server-side sorting, set to `true`, but if you want to support multi-column sorting, you can set it to `{ multiple: number }` | function \| boolean \| { compare: function, multiple: number } | - | | | sortOrder | Order of sorted values: `ascend` `descend` `null` | `ascend` \| `descend` \| null | - | | | sortIcon | Customized sort icon | (props: { sortOrder }) => ReactNode | - | 5.6.0 | | title | Title of this column | ReactNode \| ({ sortColumns, filters }) => ReactNode | - | | | width | Width of this column ([width not working?](https://github.com/ant-design/ant-design/issues/13825#issuecomment-449889241)) | string \| number | - | | | minWidth | Min width of this column, only works when `tableLayout="auto"` | number | - | 5.21.0 | | hidden | Hidden this column | boolean | false | 5.13.0 | | onCell | Set props on per cell | function(record, rowIndex) | - | | | onFilter | Function that determines if the row is displayed when filtered | function(value, record) => boolean | - | | | onHeaderCell | Set props on per header cell | function(column) | - | | ### ColumnGroup | Property | Description | Type | Default | | -------- | ------------------------- | --------- | ------- | | title | Title of the column group | ReactNode | - | ### pagination Properties for pagination. | Property | Description | Type | Default | | --- | --- | --- | --- | | placement | Specify the placement of `Pagination`, could be`topStart` \| `topCenter` \| `topEnd` \|`bottomStart` \| `bottomCenter` \| `bottomEnd` | Array | \[`bottomEnd`] | | ~~position~~ | Specify the position of `Pagination`, could be`topLeft` \| `topCenter` \| `topRight` \|`bottomLeft` \| `bottomCenter` \| `bottomRight`, please use `placement` instead | Array | \[`bottomRight`] | More about pagination, please check [`Pagination`](/components/pagination/). ### expandable Properties for expandable. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | childrenColumnName | The column contains children to display | string | children | | | columnTitle | Set the title of the expand column | ReactNode | - | 4.23.0 | | columnWidth | Set the width of the expand column | string \| number | - | | | defaultExpandAllRows | Expand all rows initially | boolean | false | | | defaultExpandedRowKeys | Initial expanded row keys | string\[] | - | | | expandedRowClassName | Expanded row's className | string \| (record, index, indent) => string | - | string: 5.22.0 | | expandedRowKeys | Current expanded row keys | string\[] | - | | | expandedRowRender | Expanded container render for each row | function(record, index, indent, expanded): ReactNode | - | | | expandIcon | Customize row expand Icon. Ref [example](https://codesandbox.io/s/fervent-bird-nuzpr) | function(props): ReactNode | - | | | expandRowByClick | Whether to expand row by clicking anywhere in the whole row | boolean | false | | | fixed | Whether the expansion icon is fixed. Optional true `left` `right` | boolean \| string | false | 4.16.0 | | indentSize | Indent size in pixels of tree data | number | 15 | | | rowExpandable | Enable row can be expandable | (record) => boolean | - | | | showExpandColumn | Show expand column | boolean | true | 4.18.0 | | onExpand | Callback executed when the row expand icon is clicked | function(expanded, record) | - | | | onExpandedRowsChange | Callback executed when the expanded rows change | function(expandedRows) | - | | | expandedRowOffset | The offset of the expanded row, setting this will force the previous columns to be fixed | number | - | 5.26.0 | ### rowSelection Properties for row selection. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | align | Set the alignment of selection column | `left` \| `right` \| `center` | `left` | 5.25.0 | | checkStrictly | Check table row precisely; parent row and children rows are not associated | boolean | true | 4.4.0 | | columnTitle | Set the title of the selection column | ReactNode \| (originalNode: ReactNode) => ReactNode | - | | | columnWidth | Set the width of the selection column | string \| number | `32px` | | | fixed | Fixed selection column on the left | boolean | - | | | getCheckboxProps | Get Checkbox or Radio props | function(record) | - | | | hideSelectAll | Hide the selectAll checkbox and custom selection | boolean | false | 4.3.0 | | preserveSelectedRowKeys | Keep selection `key` even when it removed from `dataSource` | boolean | - | 4.4.0 | | renderCell | Renderer of the table cell. Same as `render` in column | function(checked, record, index, originNode) {} | - | 4.1.0 | | selectedRowKeys | Controlled selected row keys | string\[] \| number\[] | \[] | | | selections | Custom selection [config](#selection), only displays default selections when set to `true` | object\[] \| boolean | - | | | type | `checkbox` or `radio` | `checkbox` \| `radio` | `checkbox` | | | onCell | Set props on per cell. Same as `onCell` in column | function(record, rowIndex) | - | 5.5.0 | | onChange | Callback executed when selected rows change | function(selectedRowKeys, selectedRows, info: { type }) | - | `info.type`: 4.21.0 | | onSelect | Callback executed when select/deselect one row | function(record, selected, selectedRows, nativeEvent) | - | | ### scroll | Property | Description | Type | Default | | --- | --- | --- | --- | | scrollToFirstRowOnChange | Whether to scroll to the top of the table when paging, sorting, filtering changes | boolean | - | | x | Set horizontal scrolling, can also be used to specify the width of the scroll area, could be number, percent value, true and ['max-content'](https://developer.mozilla.org/en-US/docs/Web/CSS/width#max-content) | string \| number \| true | - | | y | Set vertical scrolling, can also be used to specify the height of the scroll area, could be string or number | string \| number | - | ### selection | Property | Description | Type | Default | | --- | --- | --- | --- | | key | Unique key of this selection | string | - | | text | Display text of this selection | ReactNode | - | | onSelect | Callback executed when this selection is clicked | function(changeableRowKeys) | - | ## Using in TypeScript ```tsx import React from 'react'; import { Table } from 'antd'; import type { TableColumnsType } from 'antd'; interface User { key: number; name: string; } const columns: TableColumnsType = [ { key: 'name', title: 'Name', dataIndex: 'name', }, ]; const data: User[] = [ { key: 0, name: 'Jack', }, ]; const Demo: React.FC = () => ( <> columns={columns} dataSource={data} /> {/* JSX style usage */} dataSource={data}> key="name" title="Name" dataIndex="name" />
    ); export default Demo; ``` Here is the [CodeSandbox for TypeScript](https://codesandbox.io/s/serene-platform-0jo5t). ## Semantic DOM ## Design Token ## Note According to the [React documentation](https://react.dev/learn/rendering-lists#keeping-list-items-in-order-with-key), every child in an array should be assigned a unique key. The values inside the Table's `dataSource` and `columns` should follow this rule. By default, `dataSource[i].key` will be treated as the key value for `dataSource`. ![console warning](https://os.alipayobjects.com/rmsportal/luLdLvhPOiRpyss.png) If `dataSource[i].key` is not provided, then you should specify the primary key of dataSource value via `rowKey`, as shown below. If not, warnings like the one above will show in browser console. ```jsx // primary key is uid return ; // or return
    record.uid} />; ``` ## FAQ ### How to hide pagination when single page or no data? You can set `hideOnSinglePage` with `pagination` prop. ### Table will return to first page when filter data. Table total page count usually reduce after filter data, we by default return to first page in case of current page is out of filtered results. You may need to keep current page after filtering when fetch data from remote service, please check [this demo](https://codesandbox.io/s/yuanchengjiazaishuju-ant-design-demo-7y2uf) as workaround. Also you can use the action from extra param to determine when return to first page. ### Why Table pagination show size changer? In order to improve user experience, Pagination show size changer by default when `total > 50` since `4.1.0`. You can set `showSizeChanger=false` to disable this feature. ### Why Table fully render when state change? Table can not tell what state used in `columns.render`, so it always need fully render to avoid sync issue. You can use `column.shouldCellUpdate` to control render. ### How to handle fixed column display over the mask layout? Fixed column use `z-index` to make it over other columns. You will find sometime fixed columns also over your mask layout. You can set `z-index` on your mask layout to resolve. ### How to custom render Table Checkbox（For example, adding Tooltip）? Since `4.1.0`, You can use [`rowSelection.renderCell`](https://ant.design/components/table/#rowselection) to custom render Table Checkbox. If you want to add Tooltip, please refer to this [demo](https://codesandbox.io/s/table-row-tooltip-v79j2v). ### Why does components.body.wrapper or components.body.row report an error when virtual is enabled? Because virtual table needs to get its ref to do some calculations, so you need to use `React.forwardRef` wrapper and pass the ref to the dom --- Title: Space URL: https://ant.design/components/space --- ## When To Use - Avoid components clinging together and set a unified space. - Use Space.Compact when child form components are compactly connected and the border is collapsed (After version `antd@4.24.0` Supported). ### Difference with Flex component - Space is used to set the spacing between inline elements. It will add a wrapper element for each child element for inline alignment. Suitable for equidistant arrangement of multiple child elements in rows and columns. - Flex is used to set the layout of block-level elements. It does not add a wrapper element. Suitable for layout of child elements in vertical or horizontal direction, and provides more flexibility and control. ## Examples Basic UsageVertical SpaceSpace SizeAlignWrapseparatorCompact Mode for form componentButton Compact ModeVertical Compact ModeInput addon debugNested Space CompactDiverse ChildFlex gap style ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | align | Align items | `start` \| `end` \|`center` \|`baseline` | - | 4.2.0 | | classNames | Semantic className | [Record](#semantic-dom) | - | | | ~~direction~~ | The space direction | `vertical` \| `horizontal` | `horizontal` | 4.1.0 | | orientation | The space direction | `vertical` \| `horizontal` | `horizontal` | | | size | The space size | [Size](#size) \| [Size\[\]](#size) | `small` | 4.1.0 \| Array: 4.9.0 | | ~~split~~ | Set split, please use `separator` instead | ReactNode | - | 4.7.0 | | separator | Set separator | ReactNode | - | - | | styles | Semantic style | [Record](#semantic-dom) | - | | | vertical | Orientation, Simultaneously configure with `orientation` and prioritize `orientation` | boolean | false | - | | wrap | Auto wrap line, when `horizontal` effective | boolean | false | 4.9.0 | ### Size `'small' | 'middle' | 'large' | number` ### Space.Compact Use Space.Compact when child form components are compactly connected and the border is collapsed. The supported components are： - Button - AutoComplete - Cascader - DatePicker - Input/Input.Search - InputNumber - Select - TimePicker - TreeSelect | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | block | Option to fit width to its parent\'s width | boolean | false | 4.24.0 | | ~~direction~~ | Set direction of layout | `vertical` \| `horizontal` | `horizontal` | 4.24.0 | | orientation | Set direction of layout | `vertical` \| `horizontal` | `horizontal` | | | vertical | Orientation, Simultaneously configure with `orientation` and prioritize `orientation` | boolean | false | - | | size | Set child component size | `large` \| `middle` \| `small` | `middle` | 4.24.0 | ## Semantic DOM ## Design Token --- Title: Splitter URL: https://ant.design/components/splitter --- ## When To Use Can be used to separate areas horizontally or vertically. When you need to freely drag and adjust the size of each area. When you need to specify the maximum and minimum width and height of an area. ## Examples Basic Control mode Vertical Collapsible Control collapsible icons Multiple panels Complex combination Lazy Customize Nested in tabs Debug ## API Common props ref：[Common props](/docs/react/common-props) > The Splitter component needs to calculate the panel size through its child elements, so its child elements only support `Splitter.Panel`. ### Splitter | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic structure className | [Record](#semantic-dom) | - | 6.0.0 | | collapsibleIcon | custom collapsible icon | `{start: ReactNode; end: ReactNode}` | - | 6.0.0 | | draggerIcon | custom dragger icon | `ReactNode` | - | 6.0.0 | | ~~layout~~ | Layout direction | `horizontal` \| `vertical` | `horizontal` | - | | lazy | Lazy mode | `boolean` | `false` | 5.23.0 | | orientation | Orientation direction | `horizontal` \| `vertical` | `horizontal` | | | styles | Semantic structure style | [Record](#semantic-dom) | - | 6.0.0 | | vertical | Orientation，Simultaneously existing with `orientation`, `orientation` takes priority | boolean | `false` | | | onResize | Panel size change callback | `(sizes: number[]) => void` | - | - | | onResizeEnd | Drag end callback | `(sizes: number[]) => void` | - | - | | onResizeStart | Callback before dragging starts | `(sizes: number[]) => void` | - | - | ### Panel | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | collapsible | Quick folding | `boolean \| { start?: boolean; end?: boolean; showCollapsibleIcon?: boolean \| 'auto' }` | `false` | showCollapsibleIcon: 5.27.0 | | defaultSize | Initial panel size support number for px or 'percent%' usage | `number \| string` | - | - | | max | Maximum threshold support number for px or 'percent%' usage | `number \| string` | - | - | | min | Minimum threshold support number for px or 'percent%' usage | `number \| string` | - | - | | resizable | Whether to enable drag and drop | `boolean` | `true` | - | | size | Controlled panel size support number for px or 'percent%' usage | `number \| string` | - | - | ## Semantic DOM ## Design Token --- Title: Slider URL: https://ant.design/components/slider --- ## When To Use To input a value in a range. ## Examples Basic Slider with InputNumber Slider with icon Customize tooltip Event Graduated slider Vertical Control visible of ToolTip Reverse Draggable track Multiple handles Dynamic edit nodes Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoFocus | Whether get focus when component mounted | boolean | false | | | classNames | Semantic structure className | [Record](#semantic-dom) | - | 5.10.0 | | defaultValue | The default value of slider. When `range` is false, use number, otherwise, use \[number, number] | number \| \[number, number] | 0 \| \[0, 0] | | | disabled | If true, the slider will not be intractable | boolean | false | | | keyboard | Support using keyboard to move handlers | boolean | true | 5.2.0+ | | dots | Whether the thumb can drag over tick only | boolean | false | | | included | Make effect when `marks` not null, true means containment and false means coordinative | boolean | true | | | marks | Tick mark of Slider, type of key must be `number`, and must in closed interval \[min, max], each mark can declare its own style | object | { number: ReactNode } \| { number: { style: CSSProperties, label: ReactNode } } | | | max | The maximum value the slider can slide to | number | 100 | | | min | The minimum value the slider can slide to | number | 0 | | | orientation | Orientation | `horizontal` \| `vertical` | `horizontal` | | | range | Dual thumb mode | boolean | false | | | reverse | Reverse the component | boolean | false | | | step | The granularity the slider can step through values. Must greater than 0, and be divided by (max - min) . When `step` is `null` but exist `marks`, the valid point will only be the `mark`, `min` and `max` | number \| null | 1 | | | styles | Semantic structure style | [Record](#semantic-dom) | - | 5.10.0 | | tooltip | The tooltip relate props | [tooltip](#tooltip) | - | 4.23.0 | | value | The value of slider. When `range` is false, use number, otherwise, use \[number, number] | number \| \[number, number] | - | | | vertical | If true, the slider will be vertical. Simultaneously existing with `orientation`, `orientation` takes priority | boolean | false | | | onChangeComplete | Fire when `mouseup` or `keyup` is fired | (value) => void | - | | | onChange | Callback function that is fired when the user changes the slider's value | (value) => void | - | | ### range | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | draggableTrack | Whether range track can be drag | boolean | false | - | | editable | Dynamic edit nodes, can't be used with `draggableTrack` | boolean | false | 5.20.0 | | minCount | The minimum count of nodes | number | 0 | 5.20.0 | | maxCount | The maximum count of nodes | number | - | 5.20.0 | ### tooltip | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoAdjustOverflow | Whether to automatically adjust the popup position | boolean | true | 5.8.0 | | open | If true, Tooltip will show always, or it will not show anyway, even if dragging or hovering | boolean | - | 4.23.0 | | placement | Set Tooltip display position. Ref [Tooltip](/components/tooltip/) | string | - | 4.23.0 | | getPopupContainer | The DOM container of the Tooltip, the default behavior is to create a div element in body | (triggerNode) => HTMLElement | () => document.body | 4.23.0 | | formatter | Slider will pass its value to `formatter`, and display its value in Tooltip, and hide Tooltip when return value is null | value => ReactNode \| null | IDENTITY | 4.23.0 | ## Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ## Semantic DOM ## Design Token --- Title: Spin URL: https://ant.design/components/spin --- ## When To Use When part of the page is waiting for asynchronous data or during a rendering process, an appropriate loading animation can effectively alleviate users' inquietude. ## Examples Basic Usage Size Embedded mode Customized description Delay Custom spinning indicator Progress Fullscreen ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | delay | Specifies a delay in milliseconds for loading state (prevent flush) | number (milliseconds) | - | | fullscreen | Display a backdrop with the `Spin` component | boolean | false | 5.11.0 | | indicator | React node of the spinning indicator | ReactNode | - | | | percent | The progress percentage, when set to `auto`, it will be an indeterminate progress | number \| 'auto' | - | 5.18.0 | | size | The size of Spin, options: `small`, `default` and `large` | string | `default` | | | spinning | Whether Spin is visible | boolean | true | | | tip | Customize description content when Spin has children | ReactNode | - | | | wrapperClassName | The className of wrapper when Spin has children | string | - | | ### Static Method - `Spin.setDefaultIndicator(indicator: ReactNode)` You can define default spin element globally. ## Semantic DOM ### default ### fullscreen ## Design Token --- Title: Segmented URL: https://ant.design/components/segmented --- This component is available since `antd@4.20.0`. ## When To Use - When displaying multiple options and user can select a single option; - When switching the selected option, the content of the associated area changes. ## Examples Basic Vertical Direction Block Segmented Round shape Disabled Controlled mode Custom Render Dynamic Three sizes of Segmented With Icon With Icon only With name Controlled Synced mode Consistent height Custom component token ## API Common props ref：[Common props](/docs/react/common-props) > This component is available since `antd@4.20.0` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | block | Option to fit width to its parent\'s width | boolean | false | | | defaultValue | Default selected value | string \| number | | | | disabled | Disable all segments | boolean | false | | | onChange | The callback function that is triggered when the state changes | function(value: string \| number) | | | | options | Set children optional | string\[] \| number\[] \| SegmentedItemType\[] | [] | | | orientation | Orientation | `horizontal` \| `vertical` | `horizontal` | | | size | The size of the Segmented. | `large` \| `middle` \| `small` | `middle` | | | vertical | Orientation，Simultaneously existing with `orientation`, `orientation` takes priority | boolean | `false` | 5.21.0 | | value | Currently selected value | string \| number | | | | shape | shape of Segmented | `default` \| `round` | `default` | 5.24.0 | | name | The `name` property of all `input[type="radio"]` children. if not set, it will fallback to a randomly generated name | string | | 5.23.0 | ### SegmentedItemType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | disabled | Disabled state of segmented item | boolean | false | | | className | The additional css class | string | - | | | icon | Display icon for Segmented item | ReactNode | - | | | label | Display text for Segmented item | ReactNode | - | | | tooltip | tooltip for Segmented item | string \| [TooltipProps](../tooltip/index.en-US.md#api) | - | | | value | Value for Segmented item | string \| number | - | | ## Semantic DOM ## Design Token --- Title: Skeleton URL: https://ant.design/components/skeleton --- ## When To Use - When a resource needs long time to load. - When the component contains lots of information, such as List or Card. - Only works when loading data for the first time. - Could be replaced by Spin in any situation, but can provide a better user experience. ## Examples Basic Complex combination Active Animation Button/Avatar/Input/Image/Node Contains sub component List Custom component token ## API Common props ref：[Common props](/docs/react/common-props) ### Common API ### Skeleton | Property | Description | Type | Default | | --- | --- | --- | --- | | active | Show animation effect | boolean | false | | avatar | Show avatar placeholder | boolean \| [SkeletonAvatarProps](#skeletonavatarprops) | false | | loading | Display the skeleton when true | boolean | - | | paragraph | Show paragraph placeholder | boolean \| [SkeletonParagraphProps](#skeletonparagraphprops) | true | | round | Show paragraph and title radius when true | boolean | false | | title | Show title placeholder | boolean \| [SkeletonTitleProps](#skeletontitleprops) | true | #### SkeletonTitleProps | Property | Description | Type | Default | | -------- | ---------------------- | ---------------- | ------- | | width | Set the width of title | number \| string | - | #### SkeletonParagraphProps | Property | Description | Type | Default | | --- | --- | --- | --- | | rows | Set the row count of paragraph | number | - | | width | Set the width of paragraph. When width is an Array, it can set the width of each row. Otherwise only set the last row width | number \| string \| Array<number \| string> | - | ### Skeleton.Avatar | Property | Description | Type | Default | | --- | --- | --- | --- | | active | Show animation effect, only valid when used avatar independently | boolean | false | | shape | Set the shape of avatar | `circle` \| `square` | `circle` | | size | Set the size of avatar | number \| `large` \| `small` \| `default` | `default` | ### Skeleton.Button | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | active | Show animation effect | boolean | false | | | block | Option to fit button width to its parent width | boolean | false | 4.17.0 | | shape | Set the shape of button | `circle` \| `round` \| `square` \| `default` | - | | | size | Set the size of button | `large` \| `small` \| `default` | - | | ### Skeleton.Input | Property | Description | Type | Default | | -------- | --------------------- | ------------------------------- | ------- | | active | Show animation effect | boolean | false | | size | Set the size of input | `large` \| `small` \| `default` | - | ## Semantic DOM ### Skeleton ### Skeleton.Element ## Design Token --- Title: Result URL: https://ant.design/components/result --- ## When To Use Use when important operations need to inform the user to process the results and the feedback is more complicated. ## Examples Success Info Warning 403 404 500 Error Custom icon Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | | --- | --- | --- | --- | | extra | Operating area | ReactNode | - | | icon | Custom back icon | ReactNode | - | | status | Result status, decide icons and colors | `success` \| `error` \| `info` \| `warning` \| `404` \| `403` \| `500` | `info` | | subTitle | The subTitle | ReactNode | - | | title | The title | ReactNode | - | ## Semantic DOM ## Design Token --- Title: Radio URL: https://ant.design/components/radio --- ## When To Use - Used to select a single state from multiple options. - The difference from Select is that Radio is visible to the user and can facilitate the comparison of choice, which means there shouldn't be too many of them. ```tsx // When use Radio.Group, recommended ✅ return ( ); // No recommended 🙅🏻‍♀️ return ( A B C ); ``` ## Examples Basic disabled Radio Group Vertical Radio.Group Block Radio.Group Radio.Group group - optional radio style Radio.Group with name Size Solid radio button Badge style Wireframe Component Token Upload Debug ## API Common props ref：[Common props](/docs/react/common-props) ### Radio/Radio.Button | Property | Description | Type | Default | | --- | --- | --- | --- | | autoFocus | Whether get focus when component mounted | boolean | false | | checked | Specifies whether the radio is selected | boolean | false | | defaultChecked | Specifies the initial state: whether or not the radio is selected | boolean | false | | disabled | Disable radio | boolean | false | | value | According to value for comparison, to determine whether the selected | any | - | ### Radio.Group Radio group can wrap a group of `Radio`. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | buttonStyle | The style type of radio button | `outline` \| `solid` | `outline` | | | defaultValue | Default selected value | any | - | | | disabled | Disable all radio buttons | boolean | false | | | name | The `name` property of all `input[type="radio"]` children. If not set, it will fallback to a randomly generated name | string | - | | | options | Set children optional | string\[] \| number\[] \| Array<[CheckboxOptionType](#checkboxoptiontype)> | - | | | optionType | Set Radio optionType | `default` \| `button` | `default` | 4.4.0 | | size | The size of radio button style | `large` \| `middle` \| `small` | - | | | value | Used for setting the currently selected value | any | - | | | block | Option to fit RadioGroup width to its parent width | boolean | false | 5.21.0 | | onChange | The callback function that is triggered when the state changes | function(e:Event) | - | | ### CheckboxOptionType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | label | The text used to display as the Radio option | `string` | - | 4.4.0 | | value | The value associated with the Radio option | `string` \| `number` \| `boolean` | - | 4.4.0 | | style | The style to apply to the Radio option | `React.CSSProperties` | - | 4.4.0 | | className | className of the Radio option | `string` | - | 5.25.0 | | disabled | Specifies whether the Radio option is disabled | `boolean` | `false` | 4.4.0 | | title | Adds the Title attribute value | `string` | - | 4.4.0 | | id | Adds the Radio Id attribute value | `string` | - | 4.4.0 | | onChange | Triggered when the value of the Radio Group changes | `(e: CheckboxChangeEvent) => void;` | - | 4.4.0 | | required | Specifies whether the Radio option is required | `boolean` | `false` | 4.4.0 | ## Methods ### Radio | Name | Description | | ------- | ------------ | | blur() | Remove focus | | focus() | Get focus | ## Semantic DOM ## Design Token --- Title: Select URL: https://ant.design/components/select --- ## When To Use - A dropdown menu for displaying choices - an elegant alternative to the native `` with better performance and potential of writing simpler code style in your applications. Meanwhile, we deprecated the old usage in browser console, we will remove it in antd 6.0. ::: ```jsx // works when >=5.11.0, recommended ✅ return Sample ); ``` ## Examples Basic Usage Select with search field Custom Search multiple selection Sizes Custom dropdown options Search with sort Tags Option Group coordinate Search Box Get value of selected item Automatic tokenization Search and Select Users Prefix and Suffix Custom dropdown Hide Already Selected Variants Filled debug Custom Tag Render Custom Selected Label Render Responsive maxTagCount Big Data Status Placement Dynamic Height For Debug \_InternalPanelDoNotUseOrYouWillBeFired Options label Centered Flip + Shift Component Token Max Count ## API Common props ref：[Common props](/docs/react/common-props) ### Select props | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Customize clear icon | boolean \| { clearIcon?: ReactNode } | false | 5.8.0: Support object type | | ~autoClearSearchValue~ | Whether the current search will be cleared on selecting an item. Only applies when `mode` is set to `multiple` or `tags` | boolean | true | | | autoFocus | Get focus by default | boolean | false | | | defaultActiveFirstOption | Whether active first option by default | boolean | true | | | defaultOpen | Initial open state of dropdown | boolean | - | | | defaultValue | Initial selected option | string \| string\[] \|
    number \| number\[] \|
    LabeledValue \| LabeledValue\[] | - | | | disabled | Whether disabled select | boolean | false | | | ~~popupClassName~~ | The className of dropdown menu, use `classNames.popup.root` instead | string | - | 4.23.0 | | popupMatchSelectWidth | Determine whether the popup menu and the select input are the same width. Default set `min-width` same as input. Will ignore when value less than select width. `false` will disable virtual scroll | boolean \| number | true | 5.5.0 | | ~~dropdownRender~~ | Customize dropdown content, use `popupRender` instead | (originNode: ReactNode) => ReactNode | - | | | popupRender | Customize dropdown content | (originNode: ReactNode) => ReactNode | - | | | ~~dropdownStyle~~ | The style of dropdown menu, use `styles.popup.root` instead | CSSProperties | - | | | fieldNames | Customize node label, value, options，groupLabel field name | object | { label: `label`, value: `value`, options: `options`, groupLabel: `label` } | 4.17.0 (`groupLabel` added in 5.6.0) | | ~~filterOption~~ | If true, filter options by input, if function, filter options against it. The function will receive two arguments, `inputValue` and `option`, if the function returns `true`, the option will be included in the filtered set; Otherwise, it will be excluded | boolean \| function(inputValue, option) | true | | | ~~filterSort~~ | Sort function for search options sorting, see [Array.sort](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort)'s compareFunction | (optionA: Option, optionB: Option, info: { searchValue: string }) => number | - | `searchValue`: 5.19.0 | | getPopupContainer | Parent Node which the selector should be rendered to. Default to `body`. When position issues happen, try to modify it into scrollable content and position it relative. [Example](https://codesandbox.io/s/4j168r7jw0) | function(triggerNode) | () => document.body | | | labelInValue | Whether to embed label in value, turn the format of value from `string` to { value: string, label: ReactNode } | boolean | false | | | listHeight | Config popup height | number | 256 | | | loading | Indicate loading state | boolean | false | | | maxCount | The max number of items can be selected, only applies when `mode` is `multiple` or `tags` | number | - | 5.13.0 | | maxTagCount | Max tag count to show. `responsive` will cost render performance | number \| `responsive` | - | responsive: 4.10 | | maxTagPlaceholder | Placeholder for not showing tags | ReactNode \| function(omittedValues) | - | | | maxTagTextLength | Max tag text length to show | number | - | | | menuItemSelectedIcon | The custom menuItemSelected icon with multiple options | ReactNode | - | | | mode | Set mode of Select | `multiple` \| `tags` | - | | | notFoundContent | Specify content to show when no result matches | ReactNode | `Not Found` | | | open | Controlled open state of dropdown | boolean | - | | | ~~optionFilterProp~~ | Which prop value of option will be used for filter if filterOption is true. If `options` is set, it should be set to `label` | string | `value` | | | optionLabelProp | Which prop value of option will render as content of select. [Example](https://codesandbox.io/s/antd-reproduction-template-tk678) | string | `children` | | | options | Select options. Will get better perf than jsx definition | { label, value }\[] | - | | | optionRender | Customize the rendering dropdown options | (option: FlattenOptionData\ , info: { index: number }) => React.ReactNode | - | 5.11.0 | | placeholder | Placeholder of select | ReactNode | - | | | placement | The position where the selection box pops up | `bottomLeft` `bottomRight` `topLeft` `topRight` | bottomLeft | | | prefix | The custom prefix | ReactNode | - | 5.22.0 | | removeIcon | The custom remove icon | ReactNode | - | | | ~~searchValue~~ | The current input "search" text | string | - | | | showSearch | Whether select is searchable | boolean \| [Object](#showsearch) | single: false, multiple: true | | | size | Size of Select input | `large` \| `middle` \| `small` | `middle` | | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | suffixIcon | The custom suffix icon. Customize icon will not response click open to avoid icon designed to do other interactive. You can use `pointer-events: none` style to bypass | ReactNode | `` | | | tagRender | Customize tag render, only applies when `mode` is set to `multiple` or `tags` | (props) => ReactNode | - | | | labelRender | Customize selected label render (LabelInValueType definition see [LabelInValueType](https://github.com/react-component/select/blob/b39c28aa2a94e7754ebc570f200ab5fd33bd31e7/src/Select.tsx#L70)) | (props: LabelInValueType) => ReactNode | - | 5.15.0 | | tokenSeparators | Separator used to tokenize, only applies when `mode="tags"` | string\[] | - | | | value | Current selected option (considered as a immutable array) | string \| string\[] \|
    number \| number\[] \|
    LabeledValue \| LabeledValue\[] | - | | | variant | Variants of selector | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | virtual | Disable virtual scroll when set to false | boolean | true | 4.1.0 | | onActive | Called when keyboard or mouse interaction occurs | function(value: string \| number \| LabeledValue) | - | | | onBlur | Called when blur | function | - | | | onChange | Called when select an option or input value change | function(value, option:Option \| Array<Option>) | - | | | onClear | Called when clear | function | - | 4.6.0 | | onDeselect | Called when an option is deselected, param is the selected option's value. Only called for `multiple` or `tags`, effective in multiple or tags mode only | function(value: string \| number \| LabeledValue) | - | | | ~~onDropdownVisibleChange~~ | Called when dropdown open, use `onOpenChange` instead | (open: boolean) => void | - | | | onOpenChange | Called when dropdown open | (open: boolean) => void | - | | | onFocus | Called when focus | (event: FocusEvent) => void | - | | | onInputKeyDown | Called when key pressed | (event: KeyboardEvent) => void | - | | | onPopupScroll | Called when dropdown scrolls | (event: UIEvent) => void | - | | | ~~onSearch~~ | Callback function that is fired when input changed | function(value: string) | - | | | onSelect | Called when an option is selected, the params are option's value (or key) and option instance | function(value: string \| number \| LabeledValue, option: Option) | - | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.25.0 | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.25.0 | > Note, if you find that the drop-down menu scrolls with the page, or you need to trigger Select in other popup layers, please try to use `getPopupContainer={triggerNode => triggerNode.parentElement}` to fix the drop-down popup rendering node in the parent element of the trigger . ### showSearch | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoClearSearchValue | Whether the current search will be cleared on selecting an item. Only applies when `mode` is set to `multiple` or `tags` | boolean | true | | | filterOption | If true, filter options by input, if function, filter options against it. The function will receive two arguments, `inputValue` and `option`, if the function returns `true`, the option will be included in the filtered set; Otherwise, it will be excluded | boolean \| function(inputValue, option) | true | | | filterSort | Sort function for search options sorting, see [Array.sort](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort)'s compareFunction | (optionA: Option, optionB: Option, info: { searchValue: string }) => number | - | `searchValue`: 5.19.0 | | optionFilterProp | Which prop value of option will be used for filter if filterOption is true. If `options` is set, it should be set to `label` | string | `value` | | | searchValue | The current input "search" text | string | - | | | onSearch | Callback function that is fired when input changed | function(value: string) | - | | ### Select Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ### Option props | Property | Description | Type | Default | Version | | --------- | ------------------------------------ | ---------------- | ------- | ------- | | className | The additional class to option | string | - | | | disabled | Disable this option | boolean | false | | | title | `title` attribute of Select Option | string | - | | | value | Default to filter with this property | string \| number | - | | ### OptGroup props | Property | Description | Type | Default | Version | | --------- | ---------------------------------- | --------------- | ------- | ------- | | key | Group key | string | - | | | label | Group label | React.ReactNode | - | | | className | The additional class to option | string | - | | | title | `title` attribute of Select Option | string | - | | ## Semantic DOM ## Design Token ## FAQ ### Why sometime search will show 2 same option when in `tags` mode? It's caused by option with different `label` and `value`. You can use `optionFilterProp="label"` to change filter logic instead. ### When I click elements in dropdownRender, the select dropdown will not be closed? You can control it by `open` prop: [codesandbox](https://codesandbox.io/s/ji-ben-shi-yong-antd-4-21-7-forked-gnp4cy?file=/demo.js). ### I don't want dropdown close when click inside `dropdownRender`? Select will close when it lose focus. You can prevent event to handle this: ```tsx ``` Note: `listItemHeight` and `listHeight` are internal props. Please only modify when necessary. ### Why a11y test report missing `aria-` props? Select only create a11y auxiliary node when operating on. Please open Select and retry. For `aria-label` & `aria-labelledby` miss warning, please add related prop to Select with your own requirement. Default virtual scrolling will create a mock element to simulate an accessible binding. If a screen reader needs to fully access the entire list, you can set `virtual={false}` to disable virtual scrolling and the accessibility option will be bound to the actual element. --- Title: Rate URL: https://ant.design/components/rate --- ## When To Use - Show evaluation. - A quick rating operation on something. ## Examples Basic Half star Show copywriting Read only Clear star Other Character Customize character Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Whether to allow clear when click again | boolean | true | | | allowHalf | Whether to allow semi selection | boolean | false | | | autoFocus | If get focus when component mounted | boolean | false | | | character | The custom character of rate | ReactNode \| (RateProps) => ReactNode | <StarFilled /> | function(): 4.4.0 | | className | The custom class name of rate | string | - | | | count | Star count | number | 5 | | | defaultValue | The default value | number | 0 | | | disabled | If read only, unable to interact | boolean | false | | | keyboard | Support keyboard operation | boolean | true | 5.18.0 | | style | The custom style object of rate | CSSProperties | - | | | tooltips | Customize tooltip by each character | [TooltipProps](/components/tooltip#api)[] \| string\[] | - | | | value | The current value | number | - | | | onBlur | Callback when component lose focus | function() | - | | | onChange | Callback when select value | function(value: number) | - | | | onFocus | Callback when component get focus | function() | - | | | onHoverChange | Callback when hover item | function(value: number) | - | | | onKeyDown | Callback when keydown on component | function(event) | - | | ## Methods | Name | Description | | ------- | ------------ | | blur() | Remove focus | | focus() | Get focus | ## Design Token --- Title: Steps URL: https://ant.design/components/steps --- ## When To Use When a given task is complicated or has a certain sequence in the series of subtasks, we can decompose it into several steps to make things easier. ## Examples Basic Error status Vertical Clickable Panel Steps With icon Switch Step Title Placement and Progress Dot Style Customized Dot Style Navigation Steps Steps with progress Progress Debug Steps inside Steps Inline Steps Inline Style Combination Variant Debug Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Steps The whole of the step bar. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | | | current | To set the current step, counting from 0. You can overwrite this state by using `status` of `Step` | number | 0 | | | ~~direction~~ | To specify the direction of the step bar, `horizontal` or `vertical` | string | `horizontal` | | | iconRender | Custom render icon, please use `items.icon` first | (oriNode, info: { index, active, item }) => ReactNode | - | | | initial | Set the initial step, counting from 0 | number | 0 | | | ~~labelPlacement~~ | Place title and content with `horizontal` or `vertical` direction | string | `horizontal` | | | orientation | To specify the orientation of the step bar, `horizontal` or `vertical` | string | `horizontal` | | | percent | Progress circle percentage of current step in `process` status (only works on basic Steps) | number | - | 4.5.0 | | progressDot | Steps with progress dot style, customize the progress dot by setting it to a function. `titlePlacement` will be `vertical` | boolean \| (iconDot, { index, status, title, content }) => ReactNode | false | | | responsive | Change to vertical direction when screen width smaller than `532px` | boolean | true | | | size | To specify the size of the step bar, `default` and `small` are currently supported | string | `default` | | | status | To specify the status of current step, can be set to one of the following values: `wait` `process` `finish` `error` | string | `process` | | | styles | Semantic DOM style | [Record](#semantic-dom) | - | | | titlePlacement | Place title and content with `horizontal` or `vertical` direction | string | `horizontal` | | | type | Type of steps, can be set to one of the following values: `default` `dot` `inline` `navigation` `panel` | string | `default` | | | variant | Config style variant | `filled` \| `outlined` | `filled` | | | onChange | Trigger when Step is changed | (current) => void | - | | | items | StepItem content | [StepItem](#stepitem) | [] | 4.24.0 | ### StepItem A single step in the step bar. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | content | Description of the step, optional property | ReactNode | - | | | ~~description~~ | Description of the step, optional property | ReactNode | - | | | disabled | Disable click | boolean | false | | | icon | Icon of the step, optional property | ReactNode | - | | | status | To specify the status. It will be automatically set by `current` of `Steps` if not configured. Optional values are: `wait` `process` `finish` `error` | string | `wait` | | | subTitle | Subtitle of the step | ReactNode | - | | | title | Title of the step | ReactNode | - | | ## Semantic DOM ### Steps ### StepItem ## Design Token --- Title: Popover URL: https://ant.design/components/popover --- ## When To Use A simple popup menu to provide extra information or operations. Comparing with `Tooltip`, besides information `Popover` card can also provide action elements like links and buttons. ## Examples Basic Three ways to trigger Placement Arrow Arrow.pointAtCenter Auto Shift Controlling the close of the dialog Hover with click popover _InternalPanelDoNotUseOrYouWillBeFired Wireframe Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Param | Description | Type | Default value | Version | | ------- | ------------------- | ---------------------------- | ------------- | ------- | | content | Content of the card | ReactNode \| () => ReactNode | - | | | title | Title of the card | ReactNode \| () => ReactNode | - | | ## Note Please ensure that the child node of `Popover` accepts `onMouseEnter`, `onMouseLeave`, `onFocus`, `onClick` events. ## Semantic DOM ## Design Token ## FAQ For more questions, please refer to [Tooltip FAQ](/components/tooltip#faq). --- Title: QRCode URL: https://ant.design/components/qr-code --- ## When To Use Used when the text needs to be converted into a QR Code. ## Examples base With Icon other status custom status render Custom Render Type Custom Size Custom Color Download QRCode Error Level Advanced Usage ## API Common props ref：[Common props](/docs/react/common-props) > This component is available since `antd@5.1.0` | Property | Description | Type | Default | Version | | :-- | :-- | :-- | :-- | :-- | | value | scanned text | string | - | | type | render type | `canvas \| svg ` | `canvas` | 5.6.0 | | icon | include image url (only image link are supported) | string | - | | size | QRCode size | number | 160 | | iconSize | include image size | number \| { width: number; height: number } | 40 | 5.19.0 | | color | QRCode Color | string | `#000` | | bgColor | QRCode Background Color | string | `transparent` | 5.5.0 | | bordered | Whether has border style | boolean | `true` | | errorLevel | Error Code Level | `'L' \| 'M' \| 'Q' \| 'H' ` | `M` | | status | QRCode status | `active \| expired \| loading \| scanned` | `active` | scanned: 5.13.0 | | statusRender | custom status render | `(info: \[StatusRenderInfo](/components/qr-code-cn#statusrenderinfo)) => React.ReactNode` | 5.20.0 | | onRefresh | callback | `() => void` | - | ### StatusRenderInfo ```typescript type StatusRenderInfo = { status: QRStatus; locale: Locale['QRCode']; onRefresh?: () => void; }; ``` ## Semantic DOM ## Design Token ## FAQ ### About QRCode ErrorLevel The ErrorLevel means that the QR code can be scanned normally after being blocked, and the maximum area that can be blocked is the error correction rate. Generally, the QR code is divided into 4 error correction levels: Level `L` can correct about `7%` errors, Level `M` can correct about `15%` errors, Level `Q` can correct about `25%` errors, and Level `H` can correct about `30%` errors. When the content encoding of the QR code carries less information, in other words, when the value link is short, set different error correction levels, and the generated image will not change. > For more information, see the: [https://www.qrcode.com/en/about/error_correction](https://www.qrcode.com/en/about/error_correction.html) ### ⚠️⚠️⚠️ Cannot scan the QR code? If the QR code cannot be scanned for identification, it may be because the link address is too long, which leads to too dense pixels. You can configure the QR code to be larger through size, or shorten the link through short link services. --- Title: Popconfirm URL: https://ant.design/components/popconfirm --- ## When To Use A simple and compact dialog used for asking for user confirmation. The difference with the `confirm` modal dialog is that it's more lightweight than the static popped full-screen confirm modal. ## Examples Basic Locale text Placement Auto Shift Conditional trigger Customize icon Asynchronously close Asynchronously close on Promise _InternalPanelDoNotUseOrYouWillBeFired Wireframe ## API Common props ref：[Common props](/docs/react/common-props) | Param | Description | Type | Default value | Version | | --- | --- | --- | --- | --- | | cancelButtonProps | The cancel button props | [ButtonProps](/components/button/#api) | - | | | cancelText | The text of the Cancel button | string | `Cancel` | | | disabled | Whether show popconfirm when click its childrenNode | boolean | false | | | icon | Customize icon of confirmation | ReactNode | <ExclamationCircle /> | | | okButtonProps | The ok button props | [ButtonProps](/components/button/#api) | - | | | okText | The text of the Confirm button | string | `OK` | | | okType | Button `type` of the Confirm button | string | `primary` | | | showCancel | Show cancel button | boolean | true | 4.18.0 | | title | The title of the confirmation box | ReactNode \| () => ReactNode | - | | | description | The description of the confirmation box title | ReactNode \| () => ReactNode | - | 5.1.0 | | onCancel | A callback of cancel | function(e) | - | | | onConfirm | A callback of confirmation | function(e) | - | | | onPopupClick | A callback of popup click | function(e) | - | 5.5.0 | ## Semantic DOM ## Design Token ## FAQ For more questions, please refer to [Tooltip FAQ](/components/tooltip#faq). --- Title: Pagination URL: https://ant.design/components/pagination --- ## When To Use - When it will take a long time to load/render all items. - If you want to browse the data by navigating through pages. ## Examples Basic Align More Changer Jumper Mini size Simple mode Controlled Total number Show All Prev and next Wireframe component Token ## API Common props ref：[Common props](/docs/react/common-props) ```jsx ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | align | Align | start \| center \| end | - | 5.19.0 | | current | Current page number | number | - | | | defaultCurrent | Default initial page number | number | 1 | | | defaultPageSize | Default number of data items per page | number | 10 | | | disabled | Disable pagination | boolean | - | | | hideOnSinglePage | Whether to hide pager on single page | boolean | false | | | itemRender | To customize item's innerHTML | (page, type: 'page' \| 'prev' \| 'next', originalElement) => React.ReactNode | - | | | pageSize | Number of data items per page | number | - | | | pageSizeOptions | Specify the sizeChanger options | number\[] | \[`10`, `20`, `50`, `100`] | | | responsive | If `size` is not specified, `Pagination` would resize according to the width of the window | boolean | - | | | showLessItems | Show less page items | boolean | false | | | showQuickJumper | Determine whether you can jump to pages directly | boolean \| { goButton: ReactNode } | false | | | showSizeChanger | Determine whether to show `pageSize` select, it will be true when `total > 50` | boolean \| [SelectProps](/components/select#api) | - | SelectProps: 5.21.0 | | showTitle | Show page item's title | boolean | true | | | showTotal | To display the total number and range | function(total, range) | - | | | simple | Whether to use simple mode | boolean \| { readOnly?: boolean } | - | | | size | Specify the size of `Pagination`, can be set to `small` | `default` \| `small` | `default` | | | total | Total number of data items | number | 0 | | | onChange | Called when the page number or `pageSize` is changed, and it takes the resulting page number and pageSize as its arguments | function(page, pageSize) | - | | | onShowSizeChange | Called when `pageSize` is changed | function(current, size) | - | | ## Semantic DOM ## Design Token --- Title: Components Overview URL: https://ant.design/components/overview --- `antd` provides plenty of UI components to enrich your web applications, and we will improve components experience consistently. We also recommend some great [Third-Party Libraries](/docs/react/recommendation) additionally. --- Title: Modal URL: https://ant.design/components/modal --- ## When To Use When requiring users to interact with the application, but without jumping to a new page and interrupting the user's workflow, you can use `Modal` to create a new floating layer over the current page to get user feedback or display information. Additionally, if you need to show a simple confirmation dialog, you can use [`App.useApp`](/components/app/) hooks. ## Examples Basic Asynchronously close Customized Footer Loading Customized Footer render function Use hooks to get context Internationalization Manual to update destroy To customize the position of modal Dark Bg Customize footer buttons props Custom modal content render To customize the width of modal Static Method Static confirmation Customize className for build-in module destroy confirmation modal dialog Nested Modal \_InternalPanelDoNotUseOrYouWillBeFired Control modal's animation origin position Wireframe Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | afterClose | Specify a function that will be called when modal is closed completely | function | - | | | classNames | Config Modal build-in module's className | [Record](#semantic-dom) | - | | | styles | Config Modal build-in module's style | [Record](#semantic-dom) | - | 5.10.0 | | cancelButtonProps | The cancel button props | [ButtonProps](/components/button/#api) | - | | | cancelText | Text of the Cancel button | ReactNode | `Cancel` | | | centered | Centered Modal | boolean | false | | | closable | Whether a close (x) button is visible on top right or not | boolean \| { closeIcon?: React.ReactNode; disabled?: boolean; } | true | | | closeIcon | Custom close icon. 5.7.0: close button will be hidden when setting to `null` or `false` | ReactNode | <CloseOutlined /> | | | confirmLoading | Whether to apply loading visual effect for OK button or not | boolean | false | | | ~~destroyOnClose~~ | Whether to unmount child components on onClose | boolean | false | | | destroyOnHidden | Whether to unmount child components on onClose | boolean | false | 5.25.0 | | focusTriggerAfterClose | Whether need to focus trigger element after dialog is closed | boolean | true | 4.9.0 | | footer | Footer content, set as `footer={null}` when you don't need default buttons | ReactNode \| (originNode: ReactNode, extra: { OkBtn: React.FC, CancelBtn: React.FC }) => ReactNode | (OK and Cancel buttons) | renderFunction: 5.9.0 | | forceRender | Force render Modal | boolean | false | | | getContainer | The mounted node for Modal but still display at fullscreen | HTMLElement \| () => HTMLElement \| Selectors \| false | document.body | | | keyboard | Whether support press esc to close | boolean | true | | | mask | Whether show mask or not | boolean | true | | | maskClosable | Whether to close the modal dialog when the mask (area outside the modal) is clicked | boolean | true | | | modalRender | Custom modal content render | (node: ReactNode) => ReactNode | - | 4.7.0 | | okButtonProps | The ok button props | [ButtonProps](/components/button/#api) | - | | | okText | Text of the OK button | ReactNode | `OK` | | | okType | Button `type` of the OK button | string | `primary` | | | style | Style of floating layer, typically used at least for adjusting the position | CSSProperties | - | | | loading | Show the skeleton | boolean | | 5.18.0 | | title | The modal dialog's title | ReactNode | - | | | open | Whether the modal dialog is visible or not | boolean | false | | | width | Width of the modal dialog | string \| number \| [Breakpoint](/components/grid-cn#col) | 520 | Breakpoint: 5.23.0 | | wrapClassName | The class name of the container of the modal dialog | string | - | | | zIndex | The `z-index` of the Modal | number | 1000 | | | onCancel | Specify a function that will be called when a user clicks mask, close button on top right or Cancel button | function(e) | - | | | onOk | Specify a function that will be called when a user clicks the OK button | function(e) | - | | | afterOpenChange | Callback when the animation ends when Modal is turned on and off | (open: boolean) => void | - | 5.4.0 | #### Note - The state of Modal will be preserved at it's component lifecycle by default, if you wish to open it with a brand new state every time, set `destroyOnHidden` on it. - There is a situation that using `` with Form, which won't clear fields value when closing Modal even you have set `destroyOnHidden`. You need `
    ` in this case. - `Modal.method()` RTL mode only supports hooks. ### Modal.method() There are five ways to display the information based on the content's nature: - `Modal.info` - `Modal.success` - `Modal.error` - `Modal.warning` - `Modal.confirm` The items listed above are all functions, expecting a settings object as parameter. The properties of the object are follows: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | afterClose | Specify a function that will be called when modal is closed completely | function | - | 4.9.0 | | autoFocusButton | Specify which button to autofocus | null \| `ok` \| `cancel` | `ok` | | | cancelButtonProps | The cancel button props | [ButtonProps](/components/button/#api) | - | | | cancelText | Text of the Cancel button with Modal.confirm | string | `Cancel` | | | centered | Centered Modal | boolean | false | | | className | The className of container | string | - | | | closable | Whether a close (x) button is visible on top right of the confirm dialog or not | boolean | false | 4.9.0 | | closeIcon | Custom close icon | ReactNode | undefined | 4.9.0 | | content | Content | ReactNode | - | | | footer | Footer content, set as `footer: null` when you don't need default buttons | ReactNode \| (originNode: ReactNode, extra: { OkBtn: React.FC, CancelBtn: React.FC }) => ReactNode | - | renderFunction: 5.9.0 | | getContainer | Return the mount node for Modal | HTMLElement \| () => HTMLElement \| Selectors \| false | document.body | | | icon | Custom icon | ReactNode | <ExclamationCircleFilled /> | | | keyboard | Whether support press esc to close | boolean | true | | | mask | Whether show mask or not. | boolean | true | | | maskClosable | Whether to close the modal dialog when the mask (area outside the modal) is clicked | boolean | false | | | okButtonProps | The ok button props | [ButtonProps](/components/button/#api) | - | | | okText | Text of the OK button | string | `OK` | | | okType | Button `type` of the OK button | string | `primary` | | | style | Style of floating layer, typically used at least for adjusting the position | CSSProperties | - | | | title | Title | ReactNode | - | | | width | Width of the modal dialog | string \| number | 416 | | | wrapClassName | The class name of the container of the modal dialog | string | - | 4.18.0 | | zIndex | The `z-index` of the Modal | number | 1000 | | | onCancel | Click to onCancel the callback, the parameter is the closing function, if it returns a promise, resolve means normal closing, reject means not closing | function(close) | - | | | onOk | Click to onOk the callback, the parameter is the closing function, if it returns a promise, resolve means normal closing, reject means not closing | function(close) | - | | All the `Modal.method`s will return a reference, and then we can update and close the modal dialog by the reference. ```jsx const modal = Modal.info(); modal.update({ title: 'Updated title', content: 'Updated content', }); // on 4.8.0 or above, you can pass a function to update modal modal.update((prevConfig) => ({ ...prevConfig, title: `${prevConfig.title} (New)`, })); modal.destroy(); ``` - `Modal.destroyAll` `Modal.destroyAll()` could destroy all confirmation modal dialogs(`Modal.confirm|success|info|error|warning`). Usually, you can use it in router change event to destroy confirm modal dialog automatically without use modal reference to close( it's too complex to use for all modal dialogs) ```jsx import { browserHistory } from 'react-router'; // router change browserHistory.listen(() => { Modal.destroyAll(); }); ``` ### Modal.useModal() When you need using Context, you can use `contextHolder` which created by `Modal.useModal` to insert into children. Modal created by hooks will get all the context where `contextHolder` are. Created `modal` has the same creating function with `Modal.method`. ```jsx const [modal, contextHolder] = Modal.useModal(); React.useEffect(() => { modal.confirm({ // ... }); }, []); return
    {contextHolder}
    ; ``` `modal.confirm` return method: - `destroy`: Destroy current modal - `update`: Update current modal - `then`: (Hooks only) Promise chain call, support `await` operation ```tsx // Return `true` when click `onOk` and `false` when click `onCancel` const confirmed = await modal.confirm({ ... }); ``` ## Semantic DOM ## Design Token ## FAQ ### Why content not update when Modal closed? Modal will use memo to avoid content jumping when closed. Also, if you use Form in Modal, you can reset `initialValues` by calling `resetFields` in effect. ### Why I can not access context, redux, ConfigProvider `locale/prefixCls` in Modal.xxx? antd will dynamic create React instance by `ReactDOM.render` when call Modal methods. Whose context is different with origin code located context. When you need context info (like ConfigProvider context), you can use `Modal.useModal` to get `modal` instance and `contextHolder` node. And put it in your children: ```tsx const [modal, contextHolder] = Modal.useModal(); // then call modal.confirm instead of Modal.confirm return ( {/* contextHolder is in Context1, which means modal will get context of Context1 */} {contextHolder} {/* contextHolder is out of Context2, which means modal will not get context of Context2 */} ); ``` **Note:** You must insert `contextHolder` into your children with hooks. You can use origin method if you do not need context connection. > [App Package Component](/components/app) can be used to simplify the problem of `useModal` and other methods that need to manually implant contextHolder. ### How to set static methods prefixCls ？ You can config with [`ConfigProvider.config`](/components/config-provider#configproviderconfig-4130) --- Title: Message URL: https://ant.design/components/message --- ## When To Use - To provide feedback such as success, warning, error etc. - A message is displayed at top and center and will be dismissed automatically, as a non-interrupting light-weighted prompt. ## Examples Hooks usage (recommended) Other types of message Customize duration Message with loading indicator Promise interface Customized style Update Message Content Static method (deprecated) _InternalPanelDoNotUseOrYouWillBeFired Component Token ## API Common props ref：[Common props](/docs/react/common-props) This component provides some static methods, with usage and arguments as following: - `message.success(content, [duration], onClose)` - `message.error(content, [duration], onClose)` - `message.info(content, [duration], onClose)` - `message.warning(content, [duration], onClose)` - `message.loading(content, [duration], onClose)` | Argument | Description | Type | Default | | --- | --- | --- | --- | | content | The content of the message | ReactNode \| config | - | | duration | Time(seconds) before auto-dismiss, don't dismiss if set to 0 | number | 1.5 | | onClose | Specify a function that will be called when the message is closed | function | - | `afterClose` can be called in thenable interface: - `message[level](content, [duration]).then(afterClose)` - `message[level](content, [duration], onClose).then(afterClose)` where `level` refers one static methods of `message`. The result of `then` method will be a Promise. Supports passing parameters wrapped in an object: - `message.open(config)` - `message.success(config)` - `message.error(config)` - `message.info(config)` - `message.warning(config)` - `message.loading(config)` The properties of config are as follows: | Property | Description | Type | Default | | --- | --- | --- | --- | --- | | className | Customized CSS class | string | - | | content | The content of the message | ReactNode | - | | duration | Time(seconds) before auto-dismiss, don't dismiss if set to 0 | number | 3 | | icon | Customized Icon | ReactNode | - | | pauseOnHover | keep the timer running or not on hover | boolean | true | - | | key | The unique identifier of the Message | string \| number | - | | style | Customized inline style | [CSSProperties](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/e434515761b36830c3e58a970abf5186f005adac/types/react/index.d.ts#L794) | - | | onClick | Specify a function that will be called when the message is clicked | function | - | | onClose | Specify a function that will be called when the message is closed | function | - | ### Global static methods Methods for global configuration and destruction are also provided: - `message.config(options)` - `message.destroy()` > use `message.destroy(key)` to remove a message. #### message.config > When you use `ConfigProvider` for global configuration, the system will automatically start RTL mode by default.(4.3.0+) > > When you want to use it alone, you can start the RTL mode through the following settings. ```js message.config({ top: 100, duration: 2, maxCount: 3, rtl: true, prefixCls: 'my-message', }); ``` | Argument | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | duration | Time before auto-dismiss, in seconds | number | 3 | | | getContainer | Return the mount node for Message, but still display at fullScreen | () => HTMLElement | () => document.body | | | maxCount | Max message show, drop oldest if exceed limit | number | - | | | prefixCls | The prefix className of message node | string | `ant-message` | 4.5.0 | | rtl | Whether to enable RTL mode | boolean | false | | | top | Distance from top | string \| number | 8 | | ## Semantic DOM ## Design Token ## FAQ ### Why I can not access context, redux, ConfigProvider `locale/prefixCls/theme` in message? antd will dynamic create React instance by `ReactDOM.render` when call message methods. Whose context is different with origin code located context. When you need context info (like ConfigProvider context), you can use `message.useMessage` to get `api` instance and `contextHolder` node. And put it in your children: ```tsx const [api, contextHolder] = message.useMessage(); return ( {/* contextHolder is inside Context1 which means api will get value of Context1 */} {contextHolder} {/* contextHolder is outside Context2 which means api will **not** get value of Context2 */} ); ``` **Note:** You must insert `contextHolder` into your children with hooks. You can use origin method if you do not need context connection. > [App Package Component](/components/app) can be used to simplify the problem of `useMessage` and other methods that need to manually implant contextHolder. ### How to set static methods prefixCls ？ You can config with [`ConfigProvider.config`](/components/config-provider#configproviderconfig-4130) --- Title: Progress URL: https://ant.design/components/progress --- ## When To Use If it will take a long time to complete an operation, you can use `Progress` to show the current progress and status. - When an operation will interrupt the current interface, or it needs to run in the background for more than 2 seconds. - When you need to display the completion percentage of an operation. ## Examples Progress bar Circular progress bar Mini size progress bar Responsive circular progress bar Mini size circular progress bar Dynamic Custom text format Dashboard Progress bar with success segment Stroke Linecap Custom line gradient Progress bar with steps Circular progress bar with steps Progress size Change progress value position ## API Common props ref：[Common props](/docs/react/common-props) Properties that shared by all types. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | | | format | The template function of the content | function(percent, successPercent) | (percent) => percent + `%` | - | | percent | To set the completion percentage | number | 0 | - | | railColor | The color of unfilled part | string | - | - | | showInfo | Whether to display the progress value and the status icon | boolean | true | | status | To set the status of the Progress, options: `success` `exception` `normal` `active`(line only) | string | - | | strokeColor | The color of progress bar | string | - | - | | strokeLinecap | To set the style of the progress linecap | `round` \| `butt` \| `square`, see [stroke-linecap](https://developer.mozilla.org/docs/Web/SVG/Attribute/stroke-linecap) | `round` | - | | styles | Semantic DOM style | [Record](#semantic-dom) | - | | | success | Configs of successfully progress bar | { percent: number, strokeColor: string } | - | - | | ~~trailColor~~ | The color of unfilled part. Please use `railColor` instead | string | - | - | | type | To set the type, options: `line` `circle` `dashboard` | string | `line` | | size | Progress size | number \| \[number \| string, number] \| { width: number, height: number } \| "small" \| "default" | "default" | 5.3.0, Object: 5.18.0 | ### `type="line"` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | steps | The total step count | number | - | - | | rounding | The function to round the value | (step: number) => number | Math.round | 5.24.0 | | strokeColor | The color of progress bar, render `linear-gradient` when passing an object, could accept `string[]` when has `steps`. | string \| string[] \| { from: string; to: string; direction: string } | - | 4.21.0: `string[]` | | percentPosition | Progress value position, passed in object, `align` indicates the horizontal position of the value, `type` indicates whether the value is inside or outside the progress bar | { align: string; type: string } | { align: \"end\", type: \"outer\" } | 5.18.0 | ### `type="circle"` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | steps | The total step count.When passing an object, `count` refers to the number of steps, and `gap` refers to the distance between them.When passing number, the default value for `gap` is 2. | number \| { count: number, gap: number } | - | 5.16.0 | | strokeColor | The color of circular progress, render gradient when passing an object | string \| { number%: string } | - | - | | strokeWidth | To set the width of the circular progress, unit: percentage of the canvas width | number | 6 | - | ### `type="dashboard"` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | steps | The total step count.When passing an object, `count` refers to the number of steps, and `gap` refers to the distance between them.When passing number, the default value for `gap` is 2. | number \| { count: number, gap: number } | - | 5.16.0 | | gapDegree | The gap degree of half circle, 0 ~ 295 | number | 75 | | gapPlacement | The gap placement, options: `top` `bottom` `start` `end` | string | `bottom` | | ~~gapPosition~~ | The gap position, options: `top` `bottom` `left` `right`, please use `gapPlacement` instead | string | `bottom` | | strokeWidth | To set the width of the dashboard progress, unit: percentage of the canvas width | number | 6 | ## Semantic DOM ## Design Token --- Title: Menu URL: https://ant.design/components/menu --- ## When To Use Navigation is an important part of any website, as a good navigation setup allows users to move around the site quickly and efficiently. Ant Design offers two navigation options: top and side. Top navigation provides all the categories and functions of the website. Side navigation provides the multi-level structure of the website. More layouts with navigation: [Layout](/components/layout). ## Notes for developers - Menu is rendered as a `ul` element, so it only supports [`li` and `script-supporting` elements](https://html.spec.whatwg.org/multipage/grouping-content.html#the-ul-element) as children nodes. Your customized node should be wrapped by `Menu.Item`. - Menu needs to collect its node structure, so its children should be `Menu.*` or encapsulated HOCs. ## Examples Top Navigation Top Navigation (dark) Inline menu Collapsed inline menu Open current submenu only Vertical menu Menu Themes Sub-menu theme Switch the menu type Style debug Menu v4 Component Token Extra Style debug Custom Submenu Render ## API Common props ref：[Common props](/docs/react/common-props) ### Menu | Param | Description | Type | Default value | Version | | --- | --- | --- | --- | --- | | defaultOpenKeys | Array with the keys of default opened sub menus | string\[] | - | | | defaultSelectedKeys | Array with the keys of default selected menu items | string\[] | - | | | expandIcon | custom expand icon of submenu | ReactNode \| `(props: SubMenuProps & { isSubMenu: boolean }) => ReactNode` | - | 4.9.0 | | forceSubMenuRender | Render submenu into DOM before it becomes visible | boolean | false | | | inlineCollapsed | Specifies the collapsed status when menu is inline mode | boolean | - | | | inlineIndent | Indent (in pixels) of inline menu items on each level | number | 24 | | | items | Menu item content | [ItemType\[\]](#itemtype) | - | 4.20.0 | | mode | Type of menu | `vertical` \| `horizontal` \| `inline` | `vertical` | | | multiple | Allows selection of multiple items | boolean | false | | | openKeys | Array with the keys of currently opened sub-menus | string\[] | - | | | overflowedIndicator | Customized the ellipsis icon when menu is collapsed horizontally | ReactNode | `` | | | selectable | Allows selecting menu items | boolean | true | | | selectedKeys | Array with the keys of currently selected menu items | string\[] | - | | | style | Style of the root node | CSSProperties | - | | | subMenuCloseDelay | Delay time to hide submenu when mouse leaves (in seconds) | number | 0.1 | | | subMenuOpenDelay | Delay time to show submenu when mouse enters, (in seconds) | number | 0 | | | theme | Color theme of the menu | `light` \| `dark` | `light` | | | triggerSubMenuAction | Which action can trigger submenu open/close | `hover` \| `click` | `hover` | | | onClick | Called when a menu item is clicked | function({ key, keyPath, domEvent }) | - | | | onDeselect | Called when a menu item is deselected (multiple mode only) | function({ key, keyPath, selectedKeys, domEvent }) | - | | | onOpenChange | Called when sub-menus are opened or closed | function(openKeys: string\[]) | - | | | onSelect | Called when a menu item is selected | function({ key, keyPath, selectedKeys, domEvent }) | - | | | popupRender | Custom popup renderer for submenu | (node: ReactElement, props: { item: SubMenuProps; keys: string[] }) => ReactElement | - | | > More options in [@rc-component/menu](https://github.com/react-component/menu#api) ### ItemType > type ItemType = [MenuItemType](#menuitemtype) | [SubMenuType](#submenutype) | [MenuItemGroupType](#menuitemgrouptype) | [MenuDividerType](#menudividertype); #### MenuItemType | Param | Description | Type | Default value | Version | | -------- | ------------------------------------ | --------- | ------------- | ------- | | danger | Display the danger style | boolean | false | | | disabled | Whether menu item is disabled | boolean | false | | | extra | The extra of the menu item | ReactNode | - | 5.21.0 | | icon | The icon of the menu item | ReactNode | - | | | key | Unique ID of the menu item | string | - | | | label | Menu label | ReactNode | - | | | title | Set display title for collapsed item | string | - | | #### SubMenuType | Property | Description | Type | Default value | Version | | --- | --- | --- | --- | --- | | children | Sub-menus or sub-menu items | [ItemType\[\]](#itemtype) | - | | | disabled | Whether sub-menu is disabled | boolean | false | | | icon | Icon of sub menu | ReactNode | - | | | key | Unique ID of the sub-menu | string | - | | | label | Menu label | ReactNode | - | | | popupClassName | Sub-menu class name, not working when `mode="inline"` | string | - | | | popupOffset | Sub-menu offset, not working when `mode="inline"` | \[number, number] | - | | | theme | Color theme of the SubMenu (inherits from Menu by default) | | `light` \| `dark` | - | | | onTitleClick | Callback executed when the sub-menu title is clicked | function({ key, domEvent }) | - | | | popupRender | Custom popup renderer for current sub-menu | (node: ReactElement, props: { item: SubMenuProps; keys: string[] }) => ReactElement | - | | #### MenuItemGroupType Define `type` as `group` to make as group: ```ts const groupItem = { type: 'group', // Must have label: 'My Group', children: [], }; ``` | Param | Description | Type | Default value | Version | | -------- | ---------------------- | --------------------------------- | ------------- | ------- | | children | Sub-menu items | [MenuItemType\[\]](#menuitemtype) | - | | | label | The title of the group | ReactNode | - | | #### MenuDividerType Divider line in between menu items, only used in vertical popup Menu or Dropdown Menu. Need define the `type` as `divider`： ```ts const dividerItem = { type: 'divider', // Must have }; ``` | Param | Description | Type | Default value | Version | | ------ | ---------------------- | ------- | ------------- | ------- | | dashed | Whether line is dashed | boolean | false | | ## FAQ ### Why will Menu's children be rendered twice? Menu collects structure info with [twice-render](https://github.com/react-component/menu/blob/f4684514096d6b7123339cbe72e7b0f68db0bce2/src/Menu.tsx#L543) to support HOC usage. Merging into one render may cause the logic to become much more complex. Contributions to help improve the collection logic are welcomed. ### Why Menu do not responsive collapse in Flex layout? Menu will render fully item in flex layout and then collapse it. You need tell flex not consider Menu width to enable responsive ([online demo](https://codesandbox.io/s/ding-bu-dao-hang-antd-4-21-7-forked-5e3imy?file=/demo.js)): ```jsx
    Some Content
    ``` ## Semantic DOM ## Design Token --- Title: Notification URL: https://ant.design/components/notification --- ## When To Use To display a notification message at any of the four corners of the viewport. Typically it can be used in the following cases: - A notification with complex content. - A notification providing a feedback based on the user interaction. Or it may show some details about upcoming steps the user may have to follow. - A notification that is pushed by the application. ## Examples Hooks usage (recommended) Duration after which the notification box is closed Notification with icon Custom close button Customized Icon Placement Customized style Update Message Content Stack Show with progress Static Method (deprecated) Customize progress bar color _InternalPanelDoNotUseOrYouWillBeFired ## API Common props ref：[Common props](/docs/react/common-props) - `notification.success(config)` - `notification.error(config)` - `notification.info(config)` - `notification.warning(config)` - `notification.open(config)` - `notification.destroy(key?: String)` The properties of config are as follows: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | actions | Customized button group | ReactNode | - | 5.24.0 | | ~~btn~~ | Customized close button group, please use `actions` instead | ReactNode | - | - | | className | Customized CSS class | string | - | - | | closeIcon | Custom close icon | ReactNode | true | 5.7.0: close button will be hidden when setting to null or false | | description | The content of notification box (required) | ReactNode | - | - | | duration | Time in seconds before Notification is closed. When set to 0 or null, it will never be closed automatically | number | 4.5 | - | | showProgress | Show progress bar for auto-closing notification | boolean | | 5.18.0 | | pauseOnHover | keep the timer running or not on hover | boolean | true | 5.18.0 | | icon | Customized icon | ReactNode | - | - | | key | The unique identifier of the Notification | string | - | - | | title | The title of notification box (required) | ReactNode | - | 6.0.0 | | ~~message~~ | The title of notification box (required), please use `title` instead | ReactNode | - | - | | placement | Position of Notification, can be one of `top` \| `topLeft` \| `topRight` \| `bottom` \| `bottomLeft` \| `bottomRight` | string | `topRight` | - | | style | Customized inline style | [CSSProperties](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/e434515761b36830c3e58a970abf5186f005adac/types/react/index.d.ts#L794) | - | - | | role | The semantics of notification content recognized by screen readers. The default value is `alert`. When set as the default value, the screen reader will promptly interrupt any ongoing content reading and prioritize the notification content for immediate attention. | `alert \| status` | `alert` | 5.6.0 | | onClick | Specify a function that will be called when the notification is clicked | function | - | - | | onClose | Trigger when notification closed | function | - | - | | props | An object that can contain `data-*`, `aria-*`, or `role` props, to be put on the notification `div`. This currently only allows `data-testid` instead of `data-*` in TypeScript. See https://github.com/microsoft/TypeScript/issues/28960. | Object | - | - | - `notification.useNotification(config)` The properties of config are as follows: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | bottom | Distance from the bottom of the viewport, when `placement` is `bottom` `bottomRight` or `bottomLeft` (unit: pixels) | number | 24 | | | closeIcon | Custom close icon | ReactNode | true | 5.7.0: close button will be hidden when setting to null or false | | getContainer | Return the mount node for Notification | () => HTMLNode | () => document.body | | | placement | Position of Notification, can be one of `top` \| `topLeft` \| `topRight` \| `bottom` \| `bottomLeft` \| `bottomRight` | string | `topRight` | | | showProgress | Show progress bar for auto-closing notification | boolean | | 5.18.0 | | pauseOnHover | keep the timer running or not on hover | boolean | true | 5.18.0 | | rtl | Whether to enable RTL mode | boolean | false | | | stack | Notifications will be stacked when amount is over threshold | boolean \| `{ threshold: number }` | `{ threshold: 3 }` | 5.10.0 | | top | Distance from the top of the viewport, when `placement` is `top` `topRight` or `topLeft` (unit: pixels) | number | 24 | | | maxCount | Max Notification show, drop oldest if exceed limit | number | - | 4.17.0 | `notification` also provides a global `config()` method that can be used for specifying the default options. Once this method is used, all the notification boxes will take into account these globally defined options when displaying. ### Global configuration `notification.config(options)` > When you use `ConfigProvider` for global configuration, the system will automatically start RTL mode by default.(4.3.0+) > > When you want to use it alone, you can start the RTL mode through the following settings. #### notification.config ```js notification.config({ placement: 'bottomRight', bottom: 50, duration: 3, rtl: true, }); ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | bottom | Distance from the bottom of the viewport, when `placement` is `bottom` `bottomRight` or `bottomLeft` (unit: pixels) | number | 24 | | | closeIcon | Custom close icon | ReactNode | true | 5.7.0: close button will be hidden when setting to null or false | | duration | Time in seconds before Notification is closed. When set to 0 or null, it will never be closed automatically | number | 4.5 | | | getContainer | Return the mount node for Notification, but still display at fullScreen | () => HTMLNode | () => document.body | | | placement | Position of Notification, can be one of `top` `topLeft` `topRight` `bottom` `bottomLeft` `bottomRight` | string | `topRight` | | | showProgress | Show progress bar for auto-closing notification | boolean | | 5.18.0 | | pauseOnHover | keep the timer running or not on hover | boolean | true | 5.18.0 | | rtl | Whether to enable RTL mode | boolean | false | | | top | Distance from the top of the viewport, when `placement` is `top` `topRight` or `topLeft` (unit: pixels) | number | 24 | | | maxCount | Max Notification show, drop oldest if exceed limit | number | - | 4.17.0 | ## Semantic DOM ## Design Token ## FAQ ### Why I can not access context, redux, ConfigProvider `locale/prefixCls/theme` in notification? antd will dynamic create React instance by `ReactDOM.render` when call notification methods. Whose context is different with origin code located context. When you need context info (like ConfigProvider context), you can use `notification.useNotification` to get `api` instance and `contextHolder` node. And put it in your children: ```tsx const [api, contextHolder] = notification.useNotification(); return ( {/* contextHolder is inside Context1 which means api will get value of Context1 */} {contextHolder} {/* contextHolder is outside Context2 which means api will **not** get value of Context2 */} ); ``` **Note:** You must insert `contextHolder` into your children with hooks. You can use origin method if you do not need context connection. > [App Package Component](/components/app) can be used to simplify the problem of `useNotification` and other methods that need to manually implant contextHolder. ### How to set static methods prefixCls ？ You can config with [`ConfigProvider.config`](/components/config-provider#configproviderconfig-4130) --- Title: List URL: https://ant.design/components/list --- ## When To Use A list can be used to display content related to a single subject. The content can consist of multiple elements of varying type and size. :::warning{title=Deprecated Notice} List component has been deprecated. Will be removed in the next major version. ::: ## Examples Simple list Basic list Load more Vertical Pagination Settings Grid Test Grid Responsive grid list Scrolling loaded virtual list custom component token ## API Common props ref：[Common props](/docs/react/common-props) ### List | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | bordered | Toggles rendering of the border around the list | boolean | false | | | dataSource | DataSource array for list | any\[] | - | | | footer | List footer renderer | ReactNode | - | | | grid | The grid type of list. You can set grid to something like {gutter: 16, column: 4} | [object](#list-grid-props) | - | | | header | List header renderer | ReactNode | - | | | itemLayout | The layout of list | `horizontal` \| `vertical` | `horizontal` | | | loading | Shows a loading indicator while the contents of the list are being fetched | boolean \| [SpinProps](/components/spin/#api) ([more](https://github.com/ant-design/ant-design/issues/8659)) | false | | | loadMore | Shows a load more content | ReactNode | - | | | locale | The i18n text including empty text | object | {emptyText: `No Data`} | | | pagination | Pagination [config](/components/pagination/), hide it by setting it to false | boolean \| object | false | | | renderItem | Customize list item when using `dataSource` | (item: T, index: number) => ReactNode | - | | | rowKey | Item's unique value, could be an Item's key which holds a unique value of type `React.Key` or function that receives Item and returns a `React.Key` | `keyof` T \| (item: T) => `React.Key` | `"key"` | | | size | Size of list | `default` \| `large` \| `small` | `default` | | | split | Toggles rendering of the split under the list item | boolean | true | | ### pagination Properties for pagination. | Property | Description | Type | Default | | -------- | ----------------------------------------- | ---------------------------- | -------- | | position | The specify the position of `Pagination` | `top` \| `bottom` \| `both` | `bottom` | | align | The specify the alignment of `Pagination` | `start` \| `center` \| `end` | `end` | More about pagination, please check [`Pagination`](/components/pagination/). ### List grid props | Property | Description | Type | Default | Version | | -------- | ------------------------ | ------ | ------- | ------- | | column | The column of grid | number | - | | | gutter | The spacing between grid | number | 0 | | | xs | `<576px` column of grid | number | - | | | sm | `≥576px` column of grid | number | - | | | md | `≥768px` column of grid | number | - | | | lg | `≥992px` column of grid | number | - | | | xl | `≥1200px` column of grid | number | - | | | xxl | `≥1600px` column of grid | number | - | | ### List.Item | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | actions | The actions content of list item. If `itemLayout` is `vertical`, shows the content on bottom, otherwise shows content on the far right | Array<ReactNode> | - | | | classNames | Semantic structure className | [`Record`](#semantic-dom) | - | 5.18.0 | | extra | The extra content of list item. If `itemLayout` is `vertical`, shows the content on right, otherwise shows content on the far right | ReactNode | - | | | styles | Semantic DOM style | [`Record`](#semantic-dom) | - | 5.18.0 | ### List.Item.Meta | Property | Description | Type | Default | Version | | ----------- | ---------------------------- | --------- | ------- | ------- | | avatar | The avatar of list item | ReactNode | - | | | description | The description of list item | ReactNode | - | | | title | The title of list item | ReactNode | - | | ## Semantic DOM ## Design Token --- Title: Masonry URL: https://ant.design/components/masonry --- A masonry layout component for displaying content with different heights. ## When To Use - When displaying images or cards with irregular heights - When content needs to be evenly distributed in columns - When column count needs to be responsive ## Examples Basic Responsive Image Dynamic Fresh ## API Common props ref：[Common props](/docs/react/common-props) ## Masonry | Parameter | Description | Type | Default Value | | --- | --- | --- | --- | | classNames | Semantic structure className | [Record](#semantic-dom) | - | | columns | Number of columns, can be a fixed value or a responsive configuration | `number \| { xs?: number; sm?: number; md?: number }` | `3` | | fresh | Whether to continuously monitor the size changes of child items | `boolean` | `false` | | gutter | Spacing, can be a fixed value, responsive configuration, or a configuration for horizontal and vertical spacing | [Gap](#gap) \| \[[Gap](#gap), [Gap](#gap)\] | `0` | | items | Masonry items | [MasonryItem](#masonryitem)[] | - | | itemRender | Custom item rendering function | `(item: MasonryItem) => React.ReactNode` | - | | styles | Semantic structure style | [Record](#semantic-dom) | - | | onLayoutChange | Callback for column sorting changes | `({ key: React.Key; column: number }[]) => void` | - | ### MasonryItem | Parameter | Description | Type | Default Value | | --- | --- | --- | --- | | children | Custom display content, takes precedence over `itemRender` | `React.ReactNode` | - | | column | Specifies the column to which the item belongs | `number` | - | | data | Custom data storage | `T` | - | | height | Height of the item | `number` | - | | key | Unique identifier for the item | `string` \| `number` | - | ### Gap `Gap` represents the spacing between items. It can either be a fixed value or a responsive configuration. ```ts type Gap = undefined | number | Partial>; ``` ## Semantic DOM ## Design Token --- Title: Mentions URL: https://ant.design/components/mentions --- ## When To Use When you need to mention someone or something. ### Usage upgrade 5.1.0+ :::warning{title="Upgrade Tip"} After version 5.1.0, we provide a simpler usage `` with better performance and potential of writing simpler code style in your applications. Meanwhile, we deprecated the old usage in browser console, we will remove it in antd 6.0. ::: ```jsx // works when >=5.1.0, recommended ✅ const options = [{ value: 'sample', label: 'sample' }]; return ; // works when <5.1.0, deprecated when >=5.1.0 🙅🏻‍♀️ return ( Sample ); ``` ## Examples Basic Variants Asynchronous loading With Form Customize Trigger Token disabled or readOnly Placement With clear icon autoSize debug autoSize Status _InternalPanelDoNotUseOrYouWillBeFired Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Mention | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | If allow to remove mentions content with clear icon | boolean \| { clearIcon?: ReactNode } | false | 5.13.0 | | autoFocus | Auto get focus when component mounted | boolean | false | | | autoSize | Textarea height autosize feature, can be set to true \| false or an object { minRows: 2, maxRows: 6 } | boolean \| object | false | | | defaultValue | Default value | string | - | | | filterOption | Customize filter option logic | false \| (input: string, option: OptionProps) => boolean | - | | | getPopupContainer | Set the mount HTML node for suggestions | () => HTMLElement | - | | | notFoundContent | Set mentions content when not match | ReactNode | `Not Found` | | | placement | Set popup placement | `top` \| `bottom` | `bottom` | | | prefix | Set trigger prefix keyword | string \| string\[] | `@` | | | split | Set split string before and after selected mention | string | ` ` | | | status | Set validation status | 'error' \| 'warning' \| 'success' \| 'validating' | - | 4.19.0 | | validateSearch | Customize trigger search logic | (text: string, props: MentionsProps) => void | - | | | value | Set value of mentions | string | - | | | variant | Variants of Input | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | onBlur | Trigger when mentions lose focus | () => void | - | | | onChange | Trigger when value changed | (text: string) => void | - | | | onClear | Callback when click the clear button | () => void | - | 5.20.0 | | onFocus | Trigger when mentions get focus | () => void | - | | | onResize | The callback function that is triggered when textarea resize | function({ width, height }) | - | | | onSearch | Trigger when prefix hit | (text: string, prefix: string) => void | - | | | onSelect | Trigger when user select the option | (option: OptionProps, prefix: string) => void | - | | | onPopupScroll | Trigger when mentions scroll | (e: Event) => void | - | 5.23.0 | | options | Option Configuration | [Options](#option) | \[] | 5.1.0 | ### Mention methods | Name | Description | | ------- | ------------ | | blur() | Remove focus | | focus() | Get focus | ### Option | Property | Description | Type | Default | | --- | --- | --- | --- | | label | Title of the option | React.ReactNode | - | | key | The key value of the option | string | - | | disabled | Optional | boolean | - | | className | className | string | - | | style | The style of the option | React.CSSProperties | - | ## Semantic DOM ## Design Token --- Title: InputNumber URL: https://ant.design/components/input-number --- ## When To Use When a numeric value needs to be provided. ## Examples Basic Sizes Pre / Post tab Disabled High precision decimals Formatter Keyboard Wheel Variants Filled Debug Out of range Prefix / Suffix Status Focus Icon _InternalPanelDoNotUseOrYouWillBeFired Override Component Style ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | addonAfter | The label text displayed after (on the right side of) the input field | ReactNode | - | | | addonBefore | The label text displayed before (on the left side of) the input field | ReactNode | - | | | autoFocus | If the component gets focus when mounted | boolean | false | - | | changeOnBlur | Trigger `onChange` when blur. e.g. reset value in range by blur | boolean | true | 5.11.0 | | changeOnWheel | Allows control with mouse wheel | boolean | - | 5.14.0 | | controls | Whether to show `+-` controls, or set custom arrow icons | boolean \| { upIcon?: React.ReactNode; downIcon?: React.ReactNode; } | - | 4.19.0 | | decimalSeparator | Decimal separator | string | - | - | | placeholder | Placeholder | string | - | | | defaultValue | The initial value | number | - | - | | disabled | If the input is disabled | boolean | false | - | | formatter | Specifies the format of the value presented | function(value: number \| string, info: { userTyping: boolean, input: string }): string | - | info: 4.17.0 | | keyboard | If keyboard behavior is enabled | boolean | true | 4.12.0 | | max | The max value | number | [Number.MAX_SAFE_INTEGER](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER) | - | | min | The min value | number | [Number.MIN_SAFE_INTEGER](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MIN_SAFE_INTEGER) | - | | parser | Specifies the value extracted from formatter | function(string): number | - | - | | precision | The precision of input value. Will use `formatter` when config of `formatter` | number | - | - | | readOnly | If the input is readonly | boolean | false | - | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | prefix | The prefix icon for the Input | ReactNode | - | 4.17.0 | | suffix | The suffix icon for the Input | ReactNode | - | 5.20.0 | | size | The height of input box | `large` \| `middle` \| `small` | - | - | | step | The number to which the current value is increased or decreased. It can be an integer or decimal | number \| string | 1 | - | | stringMode | Set value as string to support high precision decimals. Will return string value by `onChange` | boolean | false | 4.13.0 | | value | The current value of the component | number | - | - | | variant | Variants of Input | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | onChange | The callback triggered when the value is changed | function(value: number \| string \| null) | - | - | | onPressEnter | The callback function that is triggered when Enter key is pressed | function(e) | - | - | | onStep | The callback function that is triggered when click up or down buttons | (value: number, info: { offset: number, type: 'up' \| 'down' }) => void | - | 4.7.0 | ## Ref | Name | Description | Type | Version | | --- | --- | --- | --- | | blur() | Remove focus | - | | | focus() | Get focus | (option?: { preventScroll?: boolean, cursor?: 'start' \| 'end' \| 'all' }) | cursor - 5.22.0 | | nativeElement | The native DOM element | - | 5.17.3 | ## Semantic DOM ## Design Token ## Notes Per issues [#21158](https://github.com/ant-design/ant-design/issues/21158), [#17344](https://github.com/ant-design/ant-design/issues/17344), [#9421](https://github.com/ant-design/ant-design/issues/9421), and [documentation about inputs](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/number#Using_number_inputs), it appears this community does not support native inclusion of the `type="number"` in the `` attributes, so please feel free to include it as needed, and be aware that it is heavily suggested that server side validation be utilized, as client side validation can be edited by power users. ## FAQ ### Why `value` can exceed `min` or `max` in control? Developer handle data by their own in control. It will make data out of sync if InputNumber changes display value. It also cause potential data issues when use in form. ### Why dynamic change `min` or `max` which makes `value` out of range will not trigger `onChange`? `onChange` is user trigger event. Auto-triggering would prevent form libraries from detecting the data modification source. ### Why `onBlur` or other event can not get correct value? InputNumber's value is wrapped by internal logic. The `event.target.value` you get from `onBlur` or other event is the DOM element's `value` instead of the actual value of InputNumber. For example, if you change the display format through `formatter` or `decimalSeparator`, you will get the formatted string in the DOM. You should always get the current value through `onChange`. ### Why `changeOnWheel` unable to control whether the mouse scroll wheel changes value? > The use of the `type` attribute is deprecated The InputNumber component allows you to use all the attributes of the input element and ultimately pass them to the input element, This attribute will also be added to the input element when you pass in `type='number'`, which will activate native behavior (allowing the mouse wheel to change the value), As a result `changeOnWheel` cannot control whether the mouse wheel changes the value. --- Title: Icon URL: https://ant.design/components/icon --- ## How to use Before using icons, you need to install the [@ant-design/icons](https://github.com/ant-design/ant-design-icons) package: :::warning{title=Tips} Remember to use @ant-design/icons v5 with antd v5. See: [#53275](https://github.com/ant-design/ant-design/issues/53275#issuecomment-2747448317) ::: ## List of icons ## Examples Basic Two-tone icon and colorful icon Custom Icon Use iconfont.cn Multiple resources from iconfont.cn ## API ### Common Icon | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | className | The className of Icon | string | - | | | rotate | Rotate by n degrees (not working in IE9) | number | - | | | spin | Rotate icon with animation | boolean | false | | | style | The style properties of icon, like `fontSize` and `color` | CSSProperties | - | | | twoToneColor | Only supports the two-tone icon. Specify the primary color | string (hex color) | - | | We still have three different themes for icons, icon component name is the icon name suffixed by the theme name. ```jsx import { StarOutlined, StarFilled, StarTwoTone } from '@ant-design/icons'; ``` ### Custom Icon | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | component | The component used for the root node | ComponentType<CustomIconComponentProps> | - | | | rotate | Rotate degrees (not working in IE9) | number | - | | | spin | Rotate icon with animation | boolean | false | | | style | The style properties of icon, like `fontSize` and `color` | CSSProperties | - | | ### About SVG icons We introduced SVG icons in version `3.9.0`, replacing font icons. This has the following benefits: - Complete offline usage of icons, without dependency on a CDN-hosted font icon file (No more empty square during downloading and no need to deploy icon font files locally either!) - Much more display accuracy on lower-resolution screens - The ability to choose icon color - No need to change built-in icons with overriding styles by providing more props in component More discussion of SVG icon reference at [#10353](https://github.com/ant-design/ant-design/issues/10353). > ⚠️ Given the extra bundle size caused by all SVG icons imported in 3.9.0, we will provide a new API to allow developers to import icons as needed, you can track [#12011](https://github.com/ant-design/ant-design/issues/12011) for updates. > > While you wait, you can use [webpack plugin](https://github.com/Beven91/webpack-ant-icon-loader) from the community to chunk the icon file. The properties `theme`, `component` and `twoToneColor` were added in `3.9.0`. The best practice is to pass the property `theme` to every `` component. ```jsx import { MessageOutlined } from '@ant-design/icons'; ; ``` All the icons will render to ``. You can still set `style` and `className` for size and color of icons. ```jsx ``` ### Set TwoTone Color When using the two-tone icons, you can use the static methods `getTwoToneColor()` and `setTwoToneColor(colorString)` to specify the primary color. ```jsx import { getTwoToneColor, setTwoToneColor } from '@ant-design/icons'; setTwoToneColor('#eb2f96'); getTwoToneColor(); // #eb2f96 ``` ### Custom Font Icon We added a `createFromIconfontCN` function to help developer use their own icons deployed at [iconfont.cn](http://iconfont.cn/) in a convenient way. > This method is specified for [iconfont.cn](http://iconfont.cn/). ```jsx import React from 'react'; import { createFromIconfontCN } from '@ant-design/icons'; import ReactDOM from 'react-dom/client'; const MyIcon = createFromIconfontCN({ scriptUrl: '//at.alicdn.com/t/font_8d5l8fzk5b87iudi.js', // generate in iconfont.cn }); ReactDOM.createRoot(mountNode).render(); ``` It creates a component that uses SVG sprites in essence. The following options are available: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | extraCommonProps | Define extra properties to the component | { \[key: string]: any } | {} | | | scriptUrl | The URL generated by [iconfont.cn](http://iconfont.cn/) project. Support `string[]` after `@ant-design/icons@4.1.0` | string \| string\[] | - | | The property `scriptUrl` should be set to import the SVG sprite symbols. See [iconfont.cn documents](http://iconfont.cn/help/detail?spm=a313x.7781069.1998910419.15&helptype=code) to learn about how to generate `scriptUrl`. ### Custom SVG Icon You can import SVG icon as a react component by using `webpack` and [`@svgr/webpack`](https://www.npmjs.com/package/@svgr/webpack). `@svgr/webpack`'s `options` [reference](https://github.com/smooth-code/svgr#options). ```js // webpack.config.js module.exports = { // ... other config test: /\.svg(\?v=\d+\.\d+\.\d+)?$/, use: [ { loader: 'babel-loader', }, { loader: '@svgr/webpack', options: { babel: false, icon: true, }, }, ], }; ``` You can import SVG icon as a react component by using `vite` and [`vite-plugin-svgr`](https://www.npmjs.com/package/vite-plugin-svgr). `@svgr/webpack`'s `options` [reference](https://github.com/smooth-code/svgr#options). ```js // vite.config.js export default defineConfig(() => ({ // ... other config plugins: [svgr({ svgrOptions: { icon: true } })], })); ``` ```jsx import React from 'react'; import Icon from '@ant-design/icons'; import MessageSvg from 'path/to/message.svg'; // path to your '*.svg' file. // import MessageSvg from 'path/to/message.svg?react'; // use vite path to your '*.svg?react' file. import ReactDOM from 'react-dom/client'; // in create-react-app: // import { ReactComponent as MessageSvg } from 'path/to/message.svg'; ReactDOM.createRoot(mountNode).render(); ``` The following properties are available for the component: | Property | Description | Type | Readonly | Version | | --- | --- | --- | --- | --- | | className | The computed class name of the `svg` element | string | - | | | fill | Define the color used to paint the `svg` element | string | `currentColor` | | | height | The height of the `svg` element | string \| number | `1em` | | | style | The computed style of the `svg` element | CSSProperties | - | | | width | The width of the `svg` element | string \| number | `1em` | | ## Design Token ## FAQ ### Why does icon style sometimes cause global style error? {#faq-icon-bad-style} Related issue: [#54391](https://github.com/ant-design/ant-design/issues/54391) When enable `layer`, icon style may deprioritize `@layer antd` and cause all components to be styled abnormally. This problem can be resolved by two steps below: 1. use `@ant-design/icons^5` instead of the latest version. 2. stop to use static methods of `message`, `Modal` 和 `notification`. use hooks version or `App` provided instance. If you must use static methods, you can put any of icon components just under `App`, what helps to avoid style impact caused by static methods. ```diff + {/* any icon */} + {/* your pages */} ``` --- Title: Input URL: https://ant.design/components/input --- ## When To Use - A user input in a form field is needed. - A search input is required. ## Examples Basic usage Three sizes of Input Variants Filled Debug Pre / Post tab Compact Style Input Group Search box Search box with loading TextArea Autosizing the height to fit the content OTP Format Tooltip Input prefix and suffix Password box With clear icon With character counting Custom count logic Status Focus Style Debug Text Align TextArea debug Pre / Post tab debug token ## API Common props ref：[Common props](/docs/react/common-props) ### Input | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | addonAfter | The label text displayed after (on the right side of) the input field | ReactNode | - | | | addonBefore | The label text displayed before (on the left side of) the input field | ReactNode | - | | | allowClear | If allow to remove input content with clear icon | boolean \| { clearIcon: ReactNode } | false | | | ~~bordered~~ | Whether has border style, please use `variant` instead | boolean | true | 4.5.0 | | classNames | Semantic DOM class | Record<[SemanticDOM](#semantic-input), string> | - | 5.4.0 | | count | Character count config | [CountConfig](#countconfig) | - | 5.10.0 | | defaultValue | The initial input content | string | - | | | disabled | Whether the input is disabled | boolean | false | | | id | The ID for input | string | - | | | maxLength | The maximum number of characters in Input | number | - | | | prefix | The prefix icon for the Input | ReactNode | - | | | showCount | Whether to show character count | boolean \| { formatter: (info: { value: string, count: number, maxLength?: number }) => ReactNode } | false | 4.18.0 info.value: 4.23.0 | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | styles | Semantic DOM style | Record<[SemanticDOM](#semantic-input), CSSProperties> | - | 5.4.0 | | size | The size of the input box. Note: in the context of a form, the `middle` size is used | `large` \| `middle` \| `small` | - | | | suffix | The suffix icon for the Input | ReactNode | - | | | type | The type of input, see: [MDN](https://developer.mozilla.org/docs/Web/HTML/Element/input#Form_%3Cinput%3E_types)( use `Input.TextArea` instead of `type="textarea"`) | string | `text` | | | value | The input content value | string | - | | | variant | Variants of Input | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | onChange | Callback when user input | function(e) | - | | | onPressEnter | The callback function that is triggered when Enter key is pressed | function(e) | - | | | onClear | Callback when click the clear button | () => void | - | 5.20.0 | > When `Input` is used in a `Form.Item` context, if the `Form.Item` has the `id` props defined then `value`, `defaultValue`, and `id` props of `Input` are automatically set. The rest of the props of Input are exactly the same as the original [input](https://reactjs.org/docs/dom-elements.html#all-supported-html-attributes). #### CountConfig ```tsx interface CountConfig { // Max character count. Different from the native `maxLength`, it will be marked warning but not truncated max?: number; // Custom character count, for example, the standard emoji length is greater than 1, you can customize the counting strategy to change it to 1 strategy?: (value: string) => number; // Same as `showCount` show?: boolean | ((args: { value: string; count: number; maxLength?: number }) => ReactNode); // Custom clipping logic when the number of characters exceeds `count.max`, no clipping when not configured exceedFormatter?: (value: string, config: { max: number }) => string; } ``` ### Input.TextArea Same as Input, and more: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoSize | Height auto size feature, can be set to true \| false or an object { minRows: 2, maxRows: 6 } | boolean \| object | false | | | classNames | Semantic DOM class | Record<[SemanticDOM](#semantic-textarea), string> | - | 5.4.0 | | styles | Semantic DOM style | Record<[SemanticDOM](#semantic-textarea), CSSProperties> | - | 5.4.0 | The rest of the props of `Input.TextArea` are the same as the original [textarea](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea). ### Input.Search | Property | Description | Type | Default | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | Record<[SemanticDOM](#semantic-search), string> | - | | | enterButton | false displays the default button color, true uses the primary color, or you can provide a custom button. Conflicts with addonAfter. | ReactNode | false | | loading | Search box with loading | boolean | false | | onSearch | The callback function triggered when you click on the search-icon, the clear-icon or press the Enter key | function(value, event, { source: "input" \| "clear" }) | - | | styles | Semantic DOM style | Record<[SemanticDOM](#semantic-search), CSSProperties> | - | | Supports all props of `Input`. ### Input.Password | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | Record<[SemanticDOM](#semantic-password), string> | - | | | iconRender | Custom toggle button | (visible) => ReactNode | (visible) => (visible ? <EyeOutlined /> : <EyeInvisibleOutlined />) | 4.3.0 | | styles | Semantic DOM style | Record<[SemanticDOM](#semantic-password), CSSProperties> | - | | | visibilityToggle | Whether show toggle button or control password visible | boolean \| [VisibilityToggle](#visibilitytoggle) | true | | ### Input.OTP Added in `5.16.0`. > Notes for developers > > When the `mask` prop is string, we recommend receiving a single character or a single emoji. If multiple characters or multiple emoji are passed, a warning will be thrown. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic DOM class | Record<[SemanticDOM](#semantic-otp), string> | - | | | defaultValue | Default value | string | - | | | disabled | Whether the input is disabled | boolean | false | | | formatter | Format display, blank fields will be filled with ` ` | (value: string) => string | - | | | separator | render the separator after the input box of the specified index | ReactNode \|((i: number) => ReactNode) | - | 5.24.0 | | styles | Semantic DOM style | Record<[SemanticDOM](#semantic-otp), CSSProperties> | - | | | mask | Custom display, the original value will not be modified | boolean \| string | `false` | `5.17.0` | | length | The number of input elements | number | 6 | | | status | Set validation status | 'error' \| 'warning' | - | | | size | The size of the input box | `small` \| `middle` \| `large` | `middle` | | | variant | Variants of Input | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | `underlined`: 5.24.0 | | value | The input content value | string | - | | | onChange | Trigger when all the fields are filled | (value: string) => void | - | | | onInput | Trigger when the input value changes | (value: string[]) => void | - | `5.22.0` | #### VisibilityToggle | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | visible | Whether the password is show or hide | boolean | false | 4.24.0 | | onVisibleChange | Callback executed when visibility of the password is changed | (visible) => void | - | 4.24.0 | #### Input Methods | Name | Description | Parameters | Version | | --- | --- | --- | --- | | blur | Remove focus | - | | | focus | Get focus | (option?: { preventScroll?: boolean, cursor?: 'start' \| 'end' \| 'all' }) | option - 4.10.0 | ## Semantic DOM ### Input {#semantic-input} ### Input.TextArea {#semantic-textarea} ### Input.Search {#semantic-search} ### Input.Password {#semantic-password} ### Input.OTP {#semantic-otp} ## Design Token ## FAQ ### Why Input lose focus when change `prefix/suffix/showCount` When Input dynamic add or remove `prefix/suffix/showCount` will make React recreate the dom structure and new input will be not focused. You can set an empty `` element to keep the dom structure: ```jsx const suffix = condition ? : ; ; ``` ### Why TextArea in control can make `value` exceed `maxLength`? When in control, component should show as what it set to avoid submit value not align with store value in Form. --- Title: Image URL: https://ant.design/components/image --- ## When To Use - When you need to display pictures. - Display when loading a large image or fault tolerant handling when loading fail. ## Examples Basic Usage Fault tolerant Progressive Loading Multiple image preview Preview from one image Custom preview image Controlled Preview Custom toolbar render Custom preview render Custom preview mask nested Top progress customization when previewing multiple images Custom component token Gets image info in the render function ## API Common props ref：[Common props](/docs/react/common-props) ### Image | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | alt | Image description | string | - | | | classNames | Custom semantic structure class names | [Record](#semantic-dom) | - | | | fallback | Fallback URL when load fails | string | - | | | height | Image height | string \| number | - | | | placeholder | Loading placeholder; if true, uses default placeholder | ReactNode | - | | | preview | Preview configuration; set to false to disable | boolean \| [PreviewType](#previewtype) | true | | | src | Image URL | string | - | | | styles | Custom semantic structure styles | [Record](#semantic-dom) | - | | | width | Image width | string \| number | - | | | onError | Callback when loading error occurs | (event: Event) => void | - | | Other Property ref [<img>](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#Attributes) ### PreviewType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | actionsRender | Custom toolbar render | (originalNode: React.ReactElement, info: ToolbarRenderInfoType) => React.ReactNode | - | | | classNames | Custom semantic structure class names | [Record](#semantic-dom) | - | | | closeIcon | Custom close icon | React.ReactNode | - | | | cover | Custom preview mask | React.ReactNode | - | | | ~~destroyOnClose~~ | Destroy child elements on preview close (removed, no longer supported) | boolean | false | | | ~~forceRender~~ | Force render preview image (removed, no longer supported) | boolean | - | | | getContainer | Specify container for preview mounting; still full screen; false mounts at current location | string \| HTMLElement \| (() => HTMLElement) \| false | - | | | imageRender | Custom preview content | (originalNode: React.ReactElement, info: { transform: [TransformType](#transformtype), image: [ImgInfo](#imginfo) }) => React.ReactNode | - | | | ~~mask~~ | Thumbnail mask, please use 'cover' instead | ReactNode | - | | | ~~maskClassName~~ | Thumbnail mask class name; please use 'classNames.cover' instead | string | - | | | maxScale | Maximum zoom scale | number | 50 | | | minScale | Minimum zoom scale | number | 1 | | | movable | Whether it is movable | boolean | true | | | open | Whether to display preview | boolean | - | | | rootClassName | Root DOM class name for preview; applies to both image and preview wrapper | string | - | | | scaleStep | Each step's zoom multiplier is 1 + scaleStep | number | 0.5 | | | src | Custom preview src | string | - | | | styles | Custom semantic structure styles | [Record](#semantic-dom) | - | | | ~~toolbarRender~~ | Custom toolbar; please use 'actionsRender' instead | (originalNode: React.ReactElement, info: Omit) => React.ReactNode | - | | | ~~visible~~ | Whether to show; please use 'open' instead | boolean | - | | | onOpenChange | Callback when preview open state changes | (visible: boolean) => void | - | | | onTransform | Callback for preview transform changes | { transform: [TransformType](#transformtype), action: [TransformAction](#transformaction) } | - | | | ~~onVisibleChange~~ | Callback when 'visible' changes; please use 'onOpenChange' instead | (visible: boolean, prevVisible: boolean) => void | - | | ### PreviewGroup | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | fallback | Fallback URL for load error | string | - | | | items | Array of preview items | string[] \| { src: string, crossOrigin: string, ... }[] | - | | | preview | Preview configuration; disable by setting to false | boolean \| [PreviewGroupType](#previewgrouptype) | true | | ### PreviewGroupType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | actionsRender | Custom toolbar render | (originalNode: React.ReactElement, info: ToolbarRenderInfoType) => React.ReactNode | - | | | classNames | Custom preview class names object | [Record](#semantic-dom) | - | | | closeIcon | Custom close icon | React.ReactNode | - | | | countRender | Custom preview count render | (current: number, total: number) => React.ReactNode | - | | | current | Index of the current preview image | number | - | | | ~~forceRender~~ | Force render preview image (removed, no longer supported) | boolean | - | | | getContainer | Specify container for preview mounting; still full screen; false mounts at current location | string \| HTMLElement \| (() => HTMLElement) \| false | - | | | imageRender | Custom preview content | (originalNode: React.ReactElement, info: { transform: [TransformType](#transformtype), image: [ImgInfo](#imginfo), current: number }) => React.ReactNode | - | | | ~~mask~~ | Thumbnail mask, please use 'cover' instead | ReactNode | - | | | ~~maskClassName~~ | Thumbnail mask class name; please use 'classNames.cover' instead | string | - | | | minScale | Minimum zoom scale | number | 1 | | | maxScale | Maximum zoom scale | number | 50 | | | movable | Whether movable | boolean | true | | | open | Whether to display preview | boolean | - | | | ~~rootClassName~~ | Root DOM class name for preview; applies to both image and preview wrapper. Use 'classNames.root' instead | string | - | | | styles | Custom semantic structure styles | [Record](#semantic-dom) | - | | | scaleStep | Each step's zoom multiplier is 1 + scaleStep | number | 0.5 | | | ~~toolbarRender~~ | Custom toolbar; please use 'actionsRender' instead | (originalNode: React.ReactElement, info: ToolbarRenderInfoType) => React.ReactNode | - | | | ~~visible~~ | Whether to show; please use 'open' instead | boolean | - | | | onOpenChange | Callback when preview open state changes, includes current preview index | (visible: boolean, info: { current: number }) => void | - | | | onChange | Callback when changing preview image | (current: number, prevCurrent: number) => void | - | | | onTransform | Callback for preview transform changes | { transform: [TransformType](#transformtype), action: [TransformAction](#transformaction) } | - | | | ~~onVisibleChange~~ | Callback when 'visible' changes; please use 'onOpenChange' instead | (visible: boolean, prevVisible: boolean, current: number) => void | - | | ## Interface ### TransformType ```typescript { x: number; y: number; rotate: number; scale: number; flipX: boolean; flipY: boolean; } ``` ### TransformAction ```typescript type TransformAction = | 'flipY' | 'flipX' | 'rotateLeft' | 'rotateRight' | 'zoomIn' | 'zoomOut' | 'close' | 'prev' | 'next' | 'wheel' | 'doubleClick' | 'move' | 'dragRebound'; ``` ### ToolbarRenderInfoType ```typescript { icons: { flipYIcon: React.ReactNode; flipXIcon: React.ReactNode; rotateLeftIcon: React.ReactNode; rotateRightIcon: React.ReactNode; zoomOutIcon: React.ReactNode; zoomInIcon: React.ReactNode; }; actions: { onActive?: (index: number) => void; // support after 5.21.0 onFlipY: () => void; onFlipX: () => void; onRotateLeft: () => void; onRotateRight: () => void; onZoomOut: () => void; onZoomIn: () => void; onReset: () => void; // support after 5.17.3 onClose: () => void; }; transform: TransformType, current: number; image: ImgInfo } ``` ### ImgInfo ```typescript { url: string; alt: string; width: string | number; height: string | number; } ``` ## Semantic DOM ## Design Token --- Title: Layout URL: https://ant.design/components/layout --- ## Specification ### Size The first level navigation is left aligned near a logo, and the secondary menu is right aligned. - Top Navigation: the height of the first level navigation is `64px`, and the second level navigation is `48px`. - Top Navigation (for landing pages): the height of the first level navigation is `80px`, and the second level navigation is `56px`. - Calculation formula of a top navigation: `48+8n`. - Calculation formula of an aside navigation: `200+8n`. ### Interaction rules - The first level navigation and the last level navigation should be distinguishable by visualization; - The current item should have the highest priority of visualization; - When the current navigation item is collapsed, the style of the current navigation item is applied to its parent level; - The left side navigation bar has support for both the accordion and expanding styles; you can choose the one that fits your case the best. ## Visualization rules Style of a navigation should conform to its level. - **Emphasis by colorblock** When the background color is a deep color, you can use this pattern for the parent level navigation item of the current page. - **The highlight match stick** When the background color is a light color, you can use this pattern for the current page navigation item; we recommend using it for the last item of the navigation path. - **Highlighted font** From the visualization aspect, a highlighted font is stronger than colorblock; this pattern is often used for the parent level of the current item. - **Enlarge the size of the font** `12px`, `14px` is a standard font size of navigation's, `14px` is used for the first and the second level of the navigation. You can choose an appropriate font size regarding the level of your navigation. ## Component Overview - `Layout`: The layout wrapper, in which `Header` `Sider` `Content` `Footer` or `Layout` itself can be nested, and can be placed in any parent container. - `Header`: The top layout with the default style, in which any element can be nested, and must be placed in `Layout`. - `Sider`: The sidebar with default style and basic functions, in which any element can be nested, and must be placed in `Layout`. - `Content`: The content layout with the default style, in which any element can be nested, and must be placed in `Layout`. - `Footer`: The bottom layout with the default style, in which any element can be nested, and must be placed in `Layout`. > Based on `flex layout`, please pay attention to the [compatibility](http://caniuse.com/#search=flex). ## Examples Basic Structure Header-Content-Footer Header-Sider Header Sider 2 Sider Custom trigger Responsive Fixed Header Fixed Sider Custom trigger debug Component Token ## API ```jsx
    header
    left sidebar main content right sidebar
    footer
     ``` ### Layout Common props ref：[Common props](/docs/react/common-props) The wrapper. | Property | Description | Type | Default | | --- | --- | --- | --- | | className | Container className | string | - | | hasSider | Whether contain Sider in children, don't have to assign it normally. Useful in ssr avoid style flickering | boolean | - | | style | To customize the styles | CSSProperties | - | ### Layout.Sider The sidebar. | Property | Description | Type | Default | | --- | --- | --- | --- | | breakpoint | [Breakpoints](/components/grid/#col) of the responsive layout | `xs` \| `sm` \| `md` \| `lg` \| `xl` \| `xxl` | - | | className | Container className | string | - | | collapsed | To set the current status | boolean | - | | collapsedWidth | Width of the collapsed sidebar, by setting to 0 a special trigger will appear | number | 80 | | collapsible | Whether can be collapsed | boolean | false | | defaultCollapsed | To set the initial status | boolean | false | | reverseArrow | Reverse direction of arrow, for a sider that expands from the right | boolean | false | | style | To customize the styles | CSSProperties | - | | theme | Color theme of the sidebar | `light` \| `dark` | `dark` | | trigger | Specify the customized trigger, set to null to hide the trigger | ReactNode | - | | width | Width of the sidebar | number \| string | 200 | | zeroWidthTriggerStyle | To customize the styles of the special trigger that appears when `collapsedWidth` is 0 | object | - | | onBreakpoint | The callback function, executed when [breakpoints](/components/grid/#api) changed | (broken) => {} | - | | onCollapse | The callback function, executed by clicking the trigger or activating the responsive layout | (collapsed, type) => {} | - | #### breakpoint width ```js { xs: '480px', sm: '576px', md: '768px', lg: '992px', xl: '1200px', xxl: '1600px', } ``` ## Design Token --- Title: Grid URL: https://ant.design/components/grid --- ## Design concept
    grid design
    In most business situations, Ant Design needs to solve a lot of information storage problems within the design area, so based on 12 Grids System, we divided the design area into 24 sections. We name the divided area 'box'. We suggest four boxes for horizontal arrangement at most, one at least. Boxes are proportional to the entire screen as shown in the picture above. To ensure a high level of visual comfort, we customize the typography inside of the box based on the box unit. ## Outline In the grid system, we define the frame outside the information area based on `row` and `column`, to ensure that every area can have stable arrangement. Following is a brief look at how it works: - Establish a set of `column` in the horizontal space defined by `row` (abbreviated col). - Your content elements should be placed directly in the `col`, and only `col` should be placed directly in `row`. - The column grid system is a value of 1-24 to represent its range spans. For example, three columns of equal width can be created by `    `. - If the sum of `col` spans in a `row` are more than 24, then the overflowing `col` as a whole will start a new line arrangement. Our grid systems base on Flex layout to allow the elements within the parent to be aligned horizontally - left, center, right, wide arrangement, and decentralized arrangement. The Grid system also supports vertical alignment - top aligned, vertically centered, bottom-aligned. You can also define the order of elements by using `order`. Layout uses a 24 grid layout to define the width of each "box", but does not rigidly adhere to the grid layout. ## Examples Basic GridGrid GutterColumn offsetGrid sortTypesettingAlignmentOrderFlex StretchResponsiveFlex ResponsiveMore responsivePlaygrounduseBreakpoint Hook ## API Common props ref：[Common props](/docs/react/common-props) If the Ant Design grid layout component does not meet your needs, you can use the excellent layout components of the community: - [react-flexbox-grid](http://roylee0704.github.io/react-flexbox-grid/) - [react-blocks](https://github.com/whoisandy/react-blocks/) ### Row | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | align | Vertical alignment | `top` \| `middle` \| `bottom` \| `stretch` \| `{[key in 'xs' \| 'sm' \| 'md' \| 'lg' \| 'xl' \| 'xxl']: 'top' \| 'middle' \| 'bottom' \| 'stretch'}` | `top` | object: 4.24.0 | | gutter | Spacing between grids, could be a number or a object like { xs: 8, sm: 16, md: 24}. Or you can use array to make horizontal and vertical spacing work at the same time `[horizontal, vertical]` | number \| object \| array | 0 | | | justify | Horizontal arrangement | `start` \| `end` \| `center` \| `space-around` \| `space-between` \| `space-evenly` \| `{[key in 'xs' \| 'sm' \| 'md' \| 'lg' \| 'xl' \| 'xxl']: 'start' \| 'end' \| 'center' \| 'space-around' \| 'space-between' \| 'space-evenly'}` | `start` | object: 4.24.0 | | wrap | Auto wrap line | boolean | true | 4.8.0 | ### Col | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | flex | Flex layout style | string \| number | - | | | offset | The number of cells to offset Col from the left | number | 0 | | | order | Raster order | number | 0 | | | pull | The number of cells that raster is moved to the left | number | 0 | | | push | The number of cells that raster is moved to the right | number | 0 | | | span | Raster number of cells to occupy, 0 corresponds to `display: none` | number | none | | | xs | `screen < 576px` and also default setting, could be a `span` value or an object containing above props | number \| object | - | | | sm | `screen ≥ 576px`, could be a `span` value or an object containing above props | number \| object | - | | | md | `screen ≥ 768px`, could be a `span` value or an object containing above props | number \| object | - | | | lg | `screen ≥ 992px`, could be a `span` value or an object containing above props | number \| object | - | | | xl | `screen ≥ 1200px`, could be a `span` value or an object containing above props | number \| object | - | | | xxl | `screen ≥ 1600px`, could be a `span` value or an object containing above props | number \| object | - | | You can modify the breakpoints values using by modifying `screen[XS|SM|MD|LG|XL|XXL]` with [theme customization](/docs/react/customize-theme) (since 5.1.0, [sandbox demo](https://codesandbox.io/s/antd-reproduction-template-forked-dlq3r9?file=/index.js)). The breakpoints of responsive grid follow [BootStrap 4 media queries rules](https://getbootstrap.com/docs/4.0/layout/overview/#responsive-breakpoints) (not including `occasionally part`). ## Design Token --- Title: Flex URL: https://ant.design/components/flex --- ## When To Use - Good for setting spacing between elements. - Suitable for setting various horizontal and vertical alignments. ### Difference with Space component - Space is used to set the spacing between inline elements. It will add a wrapper element for each child element for inline alignment. Suitable for equidistant arrangement of multiple child elements in rows and columns. - Flex is used to set the layout of block-level elements. It does not add a wrapper element. Suitable for layout of child elements in vertical or horizontal direction, and provides more flexibility and control. ## Examples BasicaligngapWrapcombinationdebug ## API > This component is available since `antd@5.10.0`. The default behavior of Flex in horizontal mode is to align upward, In vertical mode, aligns the stretch, You can adjust this via properties. Common props ref：[Common props](/docs/react/common-props) | Property | Description | type | Default | Version | | --- | --- | --- | --- | --- | | vertical | Is direction of the flex vertical, use `flex-direction: column` | boolean | `false` | | | wrap | Set whether the element is displayed in a single line or in multiple lines | [flex-wrap](https://developer.mozilla.org/en-US/docs/Web/CSS/flex-wrap) \| boolean | nowrap | boolean: 5.17.0 | | justify | Sets the alignment of elements in the direction of the main axis | [justify-content](https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content) | normal | | | align | Sets the alignment of elements in the direction of the cross axis | [align-items](https://developer.mozilla.org/en-US/docs/Web/CSS/align-items) | normal | | | flex | flex CSS shorthand properties | [flex](https://developer.mozilla.org/en-US/docs/Web/CSS/flex) | normal | | | gap | Sets the gap between grids | `small` \| `middle` \| `large` \| string \| number | - | | | component | custom element type | React.ComponentType | `div` | | | orientation | direction of the flex | `horizontal` \| `vertical` | `horizontal` | - | ## Design Token --- Title: Dropdown URL: https://ant.design/components/dropdown --- ## When To Use When there are more than a few options to choose from, you can wrap them in a `Dropdown`. By hovering or clicking on the trigger, a dropdown menu will appear, which allows you to choose an option and execute the relevant action. ## Examples BasicExtra nodePlacementArrowOther elementsArrow pointing at the centerTrigger modeClick eventButton with dropdown menuCustom dropdownCascading menuCascading menuThe way of hiding menu.Context MenuLoadingSelectable MenuMenu full styles\_InternalPanelDoNotUseOrYouWillBeFiredIcon debug ## API Common props ref：[Common props](/docs/react/common-props) ### Dropdown | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | arrow | Whether the dropdown arrow should be visible | boolean \| { pointAtCenter: boolean } | false | | | autoAdjustOverflow | Whether to adjust dropdown placement automatically when dropdown is off screen | boolean | true | 5.2.0 | | autoFocus | Focus element in `overlay` when opened | boolean | false | | | disabled | Whether the dropdown menu is disabled | boolean | - | | | ~~destroyPopupOnHide~~ | Whether destroy dropdown when hidden, use `destroyOnHidden` instead | boolean | false | | | destroyOnHidden | Whether destroy dropdown when hidden | boolean | false | 5.25.0 | | ~~dropdownRender~~ | Customize dropdown content, use `popupRender` instead | (menus: ReactNode) => ReactNode | - | 4.24.0 | | popupRender | Customize popup content | (menus: ReactNode) => ReactNode | - | 5.25.0 | | getPopupContainer | To set the container of the dropdown menu. The default is to create a div element in body, but you can reset it to the scrolling area and make a relative reposition. [Example on CodePen](https://codepen.io/afc163/pen/zEjNOy?editors=0010) | (triggerNode: HTMLElement) => HTMLElement | () => document.body | | | menu | The menu props | [MenuProps](/components/menu/#api) | - | | | ~~overlayClassName~~ | The class name of the dropdown root element, please use `classNames.root` instead | string | - | | | ~~overlayStyle~~ | The style of the dropdown root element, please use `styles.root` instead | CSSProperties | - | | | placement | Placement of popup menu: `bottom` `bottomLeft` `bottomRight` `top` `topLeft` `topRight` | string | `bottomLeft` | | | trigger | The trigger mode which executes the dropdown action. Note that hover can't be used on touchscreens | Array<`click`\|`hover`\|`contextMenu`> | \[`hover`] | | | open | Whether the dropdown menu is currently open | boolean | - | | | onOpenChange | Called when the open state is changed. Not trigger when hidden by click item | (open: boolean, info: { source: 'trigger' \| 'menu' }) => void | - | `info.source`: 5.11.0 | ## Note Please ensure that the child node of `Dropdown` accepts `onMouseEnter`, `onMouseLeave`, `onFocus`, `onClick` events. ## Semantic DOM ## Design Token ## FAQ ### How to prevent Dropdown from being squeezed when it exceeds the screen horizontally? You can use `width: max-content` style to handle this. ref [#43025](https://github.com/ant-design/ant-design/issues/43025#issuecomment-1594394135). --- Title: Form URL: https://ant.design/components/form --- ## When to use {#when-to-use} - When you need to create an instance or collect information. - When you need to validate fields in certain rules. ## Examples Basic UsageForm methodsForm LayoutForm mix layoutForm disabledForm variantsRequired styleForm sizelabel can wrapNo block ruleWatch HooksValidate TriggerValidate OnlyPath PrefixDynamic Form ItemDynamic Form nest ItemsDynamic Form nest pure ItemsComplex Dynamic Form ItemNestcomplex form controlCustomized Form ControlsStore Form Data into Upper ComponentControl between formsInline Login FormLogin FormRegistrationAdvanced searchForm in Modal to CreateTime-related ControlsHandle Form Data ManuallyCustomized ValidationDynamic RulesDependenciesgetValueProps + normalizeSlide to error fieldOther Form ControlsDisabled Input Debuglabel ellipsisTest col 24 usageRef itemCustom feedback iconsComponent Token ## API Common props ref：[Common props](/docs/react/common-props) ### Form | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | colon | Configure the default value of `colon` for Form.Item. Indicates whether the colon after the label is displayed (only effective when prop layout is horizontal) | boolean | true | | | disabled | Set form component disable, only available for antd components | boolean | false | 4.21.0 | | component | Set the Form rendering element. Do not create a DOM node for `false` | ComponentType \| false | form | | | fields | Control of form fields through state management (such as redux). Not recommended for non-strong demand. View [example](#form-demo-global-state) | [FieldData](#fielddata)\[] | - | | | form | Form control instance created by `Form.useForm()`. Automatically created when not provided | [FormInstance](#forminstance) | - | | | feedbackIcons | Can be passed custom icons while `Form.Item` element has `hasFeedback` | [FeedbackIcons](#feedbackicons) | - | 5.9.0 | | initialValues | Set value by Form initialization or reset | object | - | | | labelAlign | The text align of label of all items | `left` \| `right` | `right` | | | labelWrap | whether label can be wrap | boolean | false | 4.18.0 | | labelCol | Label layout, like `` component. Set `span` `offset` value like `{span: 3, offset: 12}` or `sm: {span: 3, offset: 12}` | [object](/components/grid/#col) | - | | | layout | Form layout | `horizontal` \| `vertical` \| `inline` | `horizontal` | | | name | Form name. Will be the prefix of Field `id` | string | - | | | preserve | Keep field value even when field removed. You can get the preserve field value by `getFieldsValue(true)` | boolean | true | 4.4.0 | | requiredMark | Required mark style. Can use required mark or optional mark. You can not config to single Form.Item since this is a Form level config | boolean \| `optional` \| ((label: ReactNode, info: { required: boolean }) => ReactNode) | true | `renderProps`: 5.9.0 | | scrollToFirstError | Auto scroll to first failed field when submit | boolean \| [Options](https://github.com/stipsan/scroll-into-view-if-needed/tree/ece40bd9143f48caf4b99503425ecb16b0ad8249#options) \| { focus: boolean } | false | focus: 5.24.0 | | size | Set field component size (antd components only) | `small` \| `middle` \| `large` | - | | | validateMessages | Validation prompt template, description [see below](#validatemessages) | [ValidateMessages](https://github.com/ant-design/ant-design/blob/6234509d18bac1ac60fbb3f92a5b2c6a6361295a/components/locale/en_US.ts#L88-L134) | - | | | validateTrigger | Config field validate trigger | string \| string\[] | `onChange` | 4.3.0 | | variant | Variant of components inside form | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | wrapperCol | The layout for input controls, same as `labelCol` | [object](/components/grid/#col) | - | | | onFieldsChange | Trigger when field updated | function(changedFields, allFields) | - | | | onFinish | Trigger after submitting the form and verifying data successfully | function(values) | - | | | onFinishFailed | Trigger after submitting the form and verifying data failed | function({ values, errorFields, outOfDate }) | - | | | onValuesChange | Trigger when value updated | function(changedValues, allValues) | - | | | clearOnDestroy | Clear form values when the form is uninstalled | boolean | false | 5.18.0 | > It accepts all props which native forms support but `onSubmit`. ### validateMessages Form provides [default verification error messages](https://github.com/ant-design/ant-design/blob/6234509d18bac1ac60fbb3f92a5b2c6a6361295a/components/locale/en_US.ts#L88-L134). You can modify the template by configuring `validateMessages` property. A common usage is to configure localization: ```jsx const validateMessages = { required: "'${name}' is required!", // ... }; ; ``` Besides, [ConfigProvider](/components/config-provider/) also provides a global configuration scheme that allows for uniform configuration error notification templates: ```jsx const validateMessages = { required: "'${name}' is Required!", // ... }; ; ``` ## Form.Item Form field component for data bidirectional binding, validation, layout, and so on. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | colon | Used with `label`, whether to display `:` after label text. | boolean | true | | | dependencies | Set the dependency field. See [below](#dependencies) | [NamePath](#namepath)\[] | - | | | extra | The extra prompt message. It is similar to help. Usage example: to display error message and prompt message at the same time | ReactNode | - | | | getValueFromEvent | Specify how to get value from event or other onChange arguments | (..args: any\[]) => any | - | | | getValueProps | Additional props with sub component (It's not recommended to generate dynamic function prop by `getValueProps`. Please pass it to child component directly) | (value: any) => Record | - | 4.2.0 | | hasFeedback | Used with `validateStatus`, this option specifies the validation status icon. Recommended to be used only with `Input`. Also, It can get feedback icons via icons prop. | boolean \| { icons: [FeedbackIcons](#feedbackicons) } | false | icons: 5.9.0 | | help | The prompt message. If not provided, the prompt message will be generated by the validation rule. | ReactNode | - | | | hidden | Whether to hide Form.Item (still collect and validate value) | boolean | false | 4.4.0 | | htmlFor | Set sub label `htmlFor` | string | - | | | initialValue | Config sub default value. Form `initialValues` get higher priority when conflict | string | - | 4.2.0 | | label | Label text. When there is no need for a label but it needs to be aligned with a colon, it can be set to null | ReactNode | - | null: 5.22.0 | | labelAlign | The text align of label, | `left` \| `right` | `right` | | | labelCol | The layout of label. You can set `span` `offset` to something like `{span: 3, offset: 12}` or `sm: {span: 3, offset: 12}` same as with ``. You can set `labelCol` on Form which will not affect nest Item. If both exists, use Item first | [object](/components/grid/#col) | - | | | messageVariables | The default validate field info, description [see below](#messagevariables) | Record<string, string> | - | 4.7.0 | | name | Field name, support array | [NamePath](#namepath) | - | | | normalize | Normalize value from component value before passing to Form instance. Do not support async | (value, prevValue, prevValues) => any | - | | | noStyle | No style for `true`, used as a pure field control. Will inherit parent Form.Item `validateStatus` if self `validateStatus` not configured | boolean | false | | | preserve | Keep field value even when field removed | boolean | true | 4.4.0 | | required | Display required style. It will be generated by the validation rule | boolean | false | | | rules | Rules for field validation. Click [here](#form-demo-basic) to see an example | [Rule](#rule)\[] | - | | | shouldUpdate | Custom field update logic. See [below](#shouldupdate) | boolean \| (prevValue, curValue) => boolean | false | | | tooltip | Config tooltip info | ReactNode \| [TooltipProps & { icon: ReactNode }](/components/tooltip#api) | - | 4.7.0 | | trigger | When to collect the value of children node. Click [here](#form-demo-customized-form-controls) to see an example | string | `onChange` | | | validateDebounce | Delay milliseconds to start validation | number | - | 5.9.0 | | validateFirst | Whether stop validate on first rule of error for this field. Will parallel validate when `parallel` configured | boolean \| `parallel` | false | `parallel`: 4.5.0 | | validateStatus | The validation status. If not provided, it will be generated by validation rule. options: `success` `warning` `error` `validating` | string | - | | | validateTrigger | When to validate the value of children node | string \| string\[] | `onChange` | | | valuePropName | Props of children node, for example, the prop of Switch or Checkbox is `checked`. This prop is an encapsulation of `getValueProps`, which will be invalid after customizing `getValueProps` | string | `value` | | | wrapperCol | The layout for input controls, same as `labelCol`. You can set `wrapperCol` on Form which will not affect nest Item. If both exists, use Item first | [object](/components/grid/#col) | - | | | layout | Form item layout | `horizontal` \| `vertical` | - | 5.18.0 | After wrapped by `Form.Item` with `name` property, `value`(or other property defined by `valuePropName`) `onChange`(or other property defined by `trigger`) props will be added to form controls, the flow of form data will be handled by Form which will cause: 1. You shouldn't use `onChange` on each form control to **collect data**(use `onValuesChange` of Form), but you can still listen to `onChange`. 2. You cannot set value for each form control via `value` or `defaultValue` prop, you should set default value with `initialValues` of Form. Note that `initialValues` cannot be updated by `setState` dynamically, you should use `setFieldsValue` in that situation. 3. You shouldn't call `setState` manually, please use `form.setFieldsValue` to change value programmatically. ### dependencies Used when there are dependencies between fields. If a field has the `dependencies` prop, this field will automatically trigger updates and validations when upstream is updated. A common scenario is a user registration form with "password" and "confirm password" fields. The "Confirm Password" validation depends on the "Password" field. After setting `dependencies`, the "Password" field update will re-trigger the validation of "Check Password". You can refer [examples](#form-demo-dependencies). `dependencies` shouldn't be used together with `shouldUpdate`, since it may result in conflicting update logic. ### FeedbackIcons `({ status: ValidateStatus, errors: ReactNode, warnings: ReactNode }) => Record` ### shouldUpdate Form updates only the modified field-related components for performance optimization purposes by incremental update. In most cases, you only need to write code or do validation with the [`dependencies`](#dependencies) property. In some specific cases, such as when a new field option appears with a field value changed, or you just want to keep some area updating by form update, you can modify the update logic of Form.Item via the `shouldUpdate`. When `shouldUpdate` is `true`, any Form update will cause the Form.Item to be re-rendered. This is very helpful for custom rendering some areas. It should be noted that the child component should be returned in a function, otherwise `shouldUpdate` won't behave correctly: related issue: [#34500](https://github.com/ant-design/ant-design/issues/34500) ```jsx {() => { return 
    {JSON.stringify(form.getFieldsValue(), null, 2)}
    ; }}     ``` You can ref [example](#form-demo-inline-login) to see detail. When `shouldUpdate` is a function, it will be called by form values update. Providing original values and current value to compare. This is very helpful for rendering additional fields based on values: ```jsx prevValues.additional !== curValues.additional}> {() => { return ( ); }} ``` You can ref [example](#form-demo-control-hooks) to see detail. ### messageVariables You can modify the default verification information of Form.Item through `messageVariables`. ```jsx user} rules={[{ required: true, message: '${label} is required' }]} > ``` Since `5.20.2`, when you don't want to convert `${}`, you can use `\\${}` to skip: ```jsx { required: true, message: '${label} is convert, \\${label} is not convert' } // good is convert, ${label} is not convert ``` ## Form.List Provides array management for fields. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | children | Render function | (fields: Field\[], operation: { add, remove, move }, meta: { errors }) => React.ReactNode | - | | | initialValue | Config sub default value. Form `initialValues` get higher priority when conflict | any\[] | - | 4.9.0 | | name | Field name, support array. List is also a field, so it will return all the values by `getFieldsValue`. You can change this logic by [config](#getfieldsvalue) | [NamePath](#namepath) | - | | | rules | Validate rules, only support customize validator. Should work with [ErrorList](#formerrorlist) | { validator, message }\[] | - | 4.7.0 | ```tsx {(fields) => (
    {fields.map((field) => ( ))}
    )}     ``` Note: You should not configure Form.Item `initialValue` under Form.List. It always should be configured by Form.List `initialValue` or Form `initialValues`. ## operation Some operator functions in render form of Form.List. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | add | add form item | (defaultValue?: any, insertIndex?: number) => void | insertIndex | 4.6.0 | | move | move form item | (from: number, to: number) => void | - | | | remove | remove form item | (index: number \| number\[]) => void | number\[] | 4.5.0 | ## Form.ErrorList New in 4.7.0. Show error messages, should only work with `rules` of Form.List. See [example](#form-demo-dynamic-form-item). | Property | Description | Type | Default | | -------- | ----------- | ------------ | ------- | | errors | Error list | ReactNode\[] | - | ## Form.Provider Provide linkage between forms. If a sub form with `name` prop update, it will auto trigger Provider related events. See [example](#form-demo-form-context). | Property | Description | Type | Default | | --- | --- | --- | --- | | onFormChange | Triggered when a sub form field updates | function(formName: string, info: { changedFields, forms }) | - | | onFormFinish | Triggered when a sub form submits | function(formName: string, info: { values, forms }) | - | ```jsx { if (name === 'form1') { // Do something... } }} >
    ...
    ...     ``` ### FormInstance | Name | Description | Type | Version | | --- | --- | --- | --- | | getFieldError | Get the error messages by the field name | (name: [NamePath](#namepath)) => string\[] | | | getFieldInstance | Get field instance | (name: [NamePath](#namepath)) => any | 4.4.0 | | getFieldsError | Get the error messages by the fields name. Return as an array | (nameList?: [NamePath](#namepath)\[]) => FieldError\[] | | | getFieldsValue | Get values by a set of field names. Return according to the corresponding structure. Default return mounted field value, but you can use `getFieldsValue(true)` to get all values | [GetFieldsValue](#getfieldsvalue) | | | getFieldValue | Get the value by the field name | (name: [NamePath](#namepath)) => any | | | isFieldsTouched | Check if fields have been operated. Check if all fields is touched when `allTouched` is `true` | (nameList?: [NamePath](#namepath)\[], allTouched?: boolean) => boolean | | | isFieldTouched | Check if a field has been operated | (name: [NamePath](#namepath)) => boolean | | | isFieldValidating | Check field if is in validating | (name: [NamePath](#namepath)) => boolean | | | resetFields | Reset fields to `initialValues` | (fields?: [NamePath](#namepath)\[]) => void | | | scrollToField | Scroll to field position | (name: [NamePath](#namepath), options: [ScrollOptions](https://github.com/stipsan/scroll-into-view-if-needed/tree/ece40bd9143f48caf4b99503425ecb16b0ad8249#options) \| { focus: boolean }) => void | focus: 5.24.0 | | setFields | Set fields status | (fields: [FieldData](#fielddata)\[]) => void | | | setFieldValue | Set fields value(Will directly pass to form store and **reset validation message**. If you do not want to modify passed object, please clone first) | (name: [NamePath](#namepath), value: any) => void | 4.22.0 | | setFieldsValue | Set fields value(Will directly pass to form store and **reset validation message**. If you do not want to modify passed object, please clone first). Use `setFieldValue` instead if you want to only config single value in Form.List | (values) => void | | | submit | Submit the form. It's same as click `submit` button | () => void | | | validateFields | Validate fields. Use `recursive` to validate all the field in the path | (nameList?: [NamePath](#namepath)\[], config?: [ValidateConfig](#validatefields)) => Promise | | #### validateFields ```tsx export interface ValidateConfig { // New in 5.5.0. Only validate content and not show error message on UI. validateOnly?: boolean; // New in 5.9.0. Recursively validate the provided `nameList` and its sub-paths. recursive?: boolean; // New in 5.11.0. Validate dirty fields (touched + validated). // It's useful to validate fields only when they are touched or validated. dirty?: boolean; } ``` return sample: ```jsx validateFields() .then((values) => { /* values: { username: 'username', password: 'password', } */ }) .catch((errorInfo) => { /* errorInfo: { values: { username: 'username', password: 'password', }, errorFields: [ { name: ['password'], errors: ['Please input your Password!'] }, ], outOfDate: false, } */ }); ``` ## Hooks ### Form.useForm `type Form.useForm = (): [FormInstance]` Create Form instance to maintain data store. ### Form.useFormInstance `type Form.useFormInstance = (): FormInstance` Added in `4.20.0`. Get current context form instance to avoid pass as props between components: ```tsx const Sub = () => { const form = Form.useFormInstance(); return
    ); }; ``` ### Form.Item.useStatus `type Form.Item.useStatus = (): { status: ValidateStatus | undefined, errors: ReactNode[], warnings: ReactNode[] }` Added in `4.22.0`. Could be used to get validate status of Form.Item. If this hook is not used under Form.Item, `status` would be `undefined`. Added `error` and `warnings` in `5.4.0`, Could be used to get error messages and warning messages of Form.Item: ```tsx const CustomInput = ({ value, onChange }) => { const { status, errors } = Form.Item.useStatus(); return ( ); }; export default () => (
    ); ``` #### Difference between other data fetching method Form only update the Field which changed to avoid full refresh perf issue. Thus you can not get real time value with `getFieldsValue` in render. And `useWatch` will rerender current component to sync with latest value. You can also use Field renderProps to get better performance if only want to do conditional render. If component no need care field value change, you can use `onValuesChange` to give to parent component to avoid current one rerender. ## Interface ### NamePath `string | number | (string | number)[]` ### GetFieldsValue `getFieldsValue` provides overloaded methods: #### getFieldsValue(nameList?: true | [NamePath](#namepath)\[], filterFunc?: FilterFunc) When `nameList` is empty, return all registered fields, including values of List (even if List has no Item children). When `nameList` is `true`, return all values in store, including unregistered fields. For example, if you set the value of an unregistered Item through `setFieldsValue`, you can also get all values through `true`. When `nameList` is an array, return the value of the specified path. Note that `nameList` is a nested array. For example, you need the value of a certain path as follows: ```tsx // Single path form.getFieldsValue([['user', 'age']]); // multiple path form.getFieldsValue([ ['user', 'age'], ['preset', 'account'], ]); ``` #### getFieldsValue({ strict?: boolean, filter?: FilterFunc }) New in `5.8.0`. Accept configuration parameters. When `strict` is `true`, only the value of Item will be matched. For example, in `{ list: [{ bamboo: 1, little: 2 }] }`, if List is only bound to the `bamboo` field, then `getFieldsValue({ strict: true })` will only get `{ list: [{ bamboo: 1 }] }`. ### FilterFunc To filter certain field values, `meta` will provide information related to the fields. For example, it can be used to retrieve values that have only been modified by the user, and so on. ```tsx type FilterFunc = (meta: { touched: boolean; validating: boolean }) => boolean; ``` ### FieldData | Name | Description | Type | | ---------- | ------------------------ | ------------------------ | | errors | Error messages | string\[] | | warnings | Warning messages | string\[] | | name | Field name path | [NamePath](#namepath)\[] | | touched | Whether is operated | boolean | | validating | Whether is in validating | boolean | | value | Field value | any | ### Rule Rule supports a config object, or a function returning config object: ```tsx type Rule = RuleConfig | ((form: FormInstance) => RuleConfig); ``` | Name | Description | Type | Version | | --- | --- | --- | --- | | defaultField | Validate rule for all array elements, valid when `type` is `array` | [rule](#rule) | | | enum | Match enum value. You need to set `type` to `enum` to enable this | any\[] | | | fields | Validate rule for child elements, valid when `type` is `array` or `object` | Record<string, [rule](#rule)> | | | len | Length of string, number, array | number | | | max | `type` required: max length of `string`, `number`, `array` | number | | | message | Error message. Will auto generate by [template](#validatemessages) if not provided | string \| ReactElement | | | min | `type` required: min length of `string`, `number`, `array` | number | | | pattern | Regex pattern | RegExp | | | required | Required field | boolean | | | transform | Transform value to the rule before validation | (value) => any | | | type | Normally `string` \|`number` \|`boolean` \|`url` \| `email`. More type to ref [here](https://github.com/react-component/async-validator#type) | string | | | validateTrigger | Set validate trigger event. Must be the sub set of `validateTrigger` in Form.Item | string \| string\[] | | | validator | Customize validation rule. Accept Promise as return. See [example](#form-demo-register) | ([rule](#rule), value) => Promise | | | warningOnly | Warning only. Not block form submit | boolean | 4.17.0 | | whitespace | Failed if only has whitespace, only work with `type: 'string'` rule | boolean | | ### WatchOptions | Name | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | form | Form instance | FormInstance | Current form in context | 5.4.0 | | preserve | Whether to watch the field which has no matched `Form.Item` | boolean | false | 5.4.0 | ## Semantic DOM ## Design Token ## FAQ ### Why can't Switch, Checkbox bind data? Form.Item default bind value to `value` prop, but Switch or Checkbox value prop is `checked`. You can use `valuePropName` to change bind value prop. ```tsx | pure ``` ### How does `name` fill value when it's an array? `name` will fill value by array order. When there exists number in it and no related field in form store, it will auto convert field to array. If you want to keep it as object, use string like: `['1', 'name']`. ### Why is there a form warning when used in Modal? > Warning: Instance created by `useForm` is not connect to any Form element. Forget to pass `form` prop? Before Modal opens, children elements do not exist in the view. You can set `forceRender` on Modal to pre-render its children. Click [here](https://codesandbox.io/s/antd-reproduction-template-ibu5c) to view an example. ### Why is component `defaultValue` not working when inside Form.Item? Components inside Form.Item with name property will turn into controlled mode, which makes `defaultValue` not work anymore. Please try `initialValues` of Form to set default value. ### Why can not call `ref` of Form at first time? `ref` only receives the mounted instance. please ref React official doc: ### Why will `resetFields` re-mount component? `resetFields` will re-mount component under Field to clean up customize component side effects (like async data, cached state, etc.). It's by design. ### Difference between Form initialValues and Item initialValue? In most case, we always recommend to use Form `initialValues`. Use Item `initialValue` only with dynamic field usage. Priority follows the rules: 1. Form `initialValues` is the first priority 2. Field `initialValue` is secondary \*. Does not work when multiple Item with same `name` setting the `initialValue` ### Why can't `getFieldsValue` get value at first render? `getFieldsValue` returns collected field data by default, but the Form.Item node is not ready at the first render. You can get all field data by `getFieldsValue(true)`. ### Why some component not response with `setFieldsValue` to `undefined`? `value` change from certain one to `undefined` in React means from controlled mode to uncontrolled mode. Thus it will not change display value but modified FormStore in fact. You can HOC to handle this: ```jsx const MyInput = ({ // Force use controlled mode value = '', ...rest }) => ; ; ``` ### Why does `onFieldsChange` trigger three times on change when field sets `rules`? Validating is also part of the value updating. It pass follow steps: 1. Trigger value change 2. Rule validating 3. Rule validated In each `onFieldsChange`, you will get `false` > `true` > `false` with `isFieldValidating`. ### Why doesn't Form.List support `label` and need ErrorList to show errors? Form.List use renderProps which mean internal structure is flexible. Thus `label` and `error` can not have best place. If you want to use antd `label`, you can wrap with Form.Item instead. ### Why can't Form.Item `dependencies` work on Form.List field? Your name path should also contain Form.List `name`: ```tsx {(fields) => fields.map((field) => ( )) } ``` dependencies should be `['users', 0, 'name']` ### Why doesn't `normalize` support async? React can not get correct interaction of controlled component with async value update. When user trigger `onChange`, component will do no response since `value` update is async. If you want to trigger value update async, you should use customize component to handle value state internal and pass sync value control to Form instead. ### `scrollToFirstError` and `scrollToField` not working? 1. use custom form control See similar issues: [#28370](https://github.com/ant-design/ant-design/issues/28370) [#27994](https://github.com/ant-design/ant-design/issues/27994) Starting from version `5.17.0`, the sliding operation will prioritize using the ref element forwarded by the form control elements. Therefore, when considering custom components to support verification scrolling, please consider forwarding it to the form control elements first. `scrollToFirstError` and `scrollToField` deps on `id` attribute passed to form control, please make sure that it hasn't been ignored in your custom form control. Check [codesandbox](https://codesandbox.io/s/antd-reproduction-template-forked-25nul?file=/index.js) for solution. 2. multiple forms on same page If there are multiple forms on the page, and there are duplicate same `name` form item, the form scroll probably may find the form item with the same name in another form. You need to set a different `name` for the `Form` component to distinguish it. ### Continue, why not use `ref` to bind element? Form can not get real DOM node when customize component not support `ref`. It will get warning in React Strict Mode if wrap with Class Component and call `findDOMNode`. So we use `id` to locate element. ### `setFieldsValue` do not trigger `onFieldsChange` or `onValuesChange`? It's by design. Only user interactive can trigger the change event. This design is aim to avoid call `setFieldsValue` in change event which may makes loop calling. ### Why Form.Item not update value when children is nest? Form.Item will inject `value` and `onChange` to children when render. Once your field component is wrapped, props will not pass to the correct node. Follow code will not work as expect: ```jsx

    I am a wrapped Input

     ``` You can use HOC to solve this problem, don't forget passing props to form control component: ```jsx const MyInput = (props) => (

    I am a wrapped Input

    ); ; ``` ### Why does clicking the label in the form change the component state? > Related issue: [#47031](https://github.com/ant-design/ant-design/issues/47031), [#43175](https://github.com/ant-design/ant-design/issues/43175), [#52152](https://github.com/ant-design/ant-design/issues/52152) Form label use [HTML label](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label) elements to wrap form controls, which focuses the corresponding control when clicked. This is the native behavior of label elements, designed to improve accessibility and user experience. This standard interaction pattern makes it easier for users to interact with form controls. If you need to disable this behavior, you can use `htmlFor={null}`, though it's generally not recommended. ```diff - + ``` --- Title: Drawer URL: https://ant.design/components/drawer --- ## When To Use A Drawer is a panel that is typically overlaid on top of a page and slides in from the side. It contains a set of information or actions. Since the user can interact with the Drawer without leaving the current page, tasks can be achieved more efficiently within the same context. - Use a Form to create or edit a set of information. - Processing subtasks. When subtasks are too heavy for a Popover and we still want to keep the subtasks in the context of the main task, Drawer comes very handy. - When the same Form is needed in multiple places. > Notes for developers > > Since the `5.17.0`, we provided the `loading` prop by the Spin. However, since the `5.18.0` version, we have fixed this design error and replaced the Spin with the Skeleton, and also modified the type of `loading` prop, which can only accept `boolean` type. ## Examples Basic Custom Placement Loading Extra Actions Render in current dom Submit form in drawer Preview drawer Multi-level drawer Preset size Customize className for build-in module ConfigProvider No mask _InternalPanelDoNotUseOrYouWillBeFired Scroll Debug Component Token ## API Common props ref：[Common props](/docs/react/common-props) :::warning{title=Note} v5 uses `rootClassName` & `rootStyle` to configure the outermost element style, instead of `className` & `style` from v4. This is done to align the API with Modal. ::: | Props | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoFocus | Whether Drawer should get focused after open | boolean | true | 4.17.0 | | afterOpenChange | Callback after the animation ends when switching drawers | function(open) | - | | | className | Config Drawer Panel className. Use `rootClassName` if want to config top DOM style | string | - | | | classNames | Semantic structure className | [Record](#semantic-dom) | - | 5.10.0 | | closeIcon | Custom close icon. 5.7.0: close button will be hidden when setting to `null` or `false` | ReactNode | <CloseOutlined /> | | | ~~destroyOnClose~~ | Whether to unmount child components on closing drawer or not | boolean | false | | | destroyOnHidden | Whether to unmount child components on closing drawer or not | boolean | false | 5.25.0 | | extra | Extra actions area at corner | ReactNode | - | 4.17.0 | | footer | The footer for Drawer | ReactNode | - | | | forceRender | Pre-render Drawer component forcibly | boolean | false | | | getContainer | mounted node and display window for Drawer | HTMLElement \| () => HTMLElement \| Selectors \| false | body | | | headerStyle | Style of the drawer header part | CSSProperties | - | | | height | Placement is `top` or `bottom`, height of the Drawer dialog | string \| number | 378 | | | keyboard | Whether support press esc to close | boolean | true | | | mask | Whether to show mask or not | boolean | true | | | maskClosable | Clicking on the mask (area outside the Drawer) to close the Drawer or not | boolean | true | | | placement | The placement of the Drawer | `top` \| `right` \| `bottom` \| `left` | `right` | | | push | Nested drawers push behavior | boolean \| { distance: string \| number } | { distance: 180 } | 4.5.0+ | | rootStyle | Style of wrapper element which **contains mask** compare to `style` | CSSProperties | - | | | style | Style of Drawer panel. Use `styles.body` if want to config body only | CSSProperties | - | | | styles | Semantic structure style | [Record](#semantic-dom) | - | 5.10.0 | | size | preset size of drawer, default `378px` and large `736px` | 'default' \| 'large' | 'default' | 4.17.0 | | title | The title for Drawer | ReactNode | - | | | loading | Show the Skeleton | boolean | false | 5.17.0 | | open | Whether the Drawer dialog is visible or not | boolean | false | | | width | Width of the Drawer dialog | string \| number | 378 | | | zIndex | The `z-index` of the Drawer | number | 1000 | | | onClose | Specify a callback that will be called when a user clicks mask, close button or Cancel button | function(e) | - | | | drawerRender | Custom drawer content render | (node: ReactNode) => ReactNode | - | 5.18.0 | ## Semantic DOM ## Design Token --- Title: Divider URL: https://ant.design/components/divider --- ## When To Use - Divide sections of an article. - Divide inline text and links such as the operation column of table. ## Examples Horizontal Divider with title Set the spacing size of the divider Text without heading style Vertical Style Customization Component Token Variant ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | children | The wrapped title | ReactNode | - | | | className | The className of container | string | - | | | dashed | Whether line is dashed | boolean | false | | | orientation | Whether line is horizontal or vertical | `horizontal` \| `vertical` | `horizontal` | - | | ~~orientationMargin~~ | The margin-left/right between the title and its closest border, while the `titlePlacement` should not be `center`, If a numeric value of type `string` is provided without a unit, it is assumed to be in pixels (px) by default. | string \| number | - | | | plain | Divider text show as plain style | boolean | true | 4.2.0 | | style | The style object of container | CSSProperties | - | | | size | The size of divider. Only valid for horizontal layout | `small` \| `middle` \| `large` | - | 5.25.0 | | titlePlacement | The position of title inside divider | `start` \| `end` \| `center` | `center` | - | | ~~type~~ | The direction type of divider | `horizontal` \| `vertical` | `horizontal` | - | | variant | Whether line is dashed, dotted or solid | `dashed` \| `dotted` \| `solid` | solid | 5.20.0 | | vertical | Orientation, Simultaneously configure with `orientation` and prioritize `orientation` | boolean | false | - | ## Semantic DOM ## Design Token --- Title: FloatButton URL: https://ant.design/components/float-button --- ## When To Use - For global functionality on the site. - Buttons that can be seen wherever you browse. ## Examples Basic Type Shape Content FloatButton with tooltip FloatButton Group Menu mode Controlled mode placement BackTop badge debug dot \_InternalPanelDoNotUseOrYouWillBeFired ## API Common props ref：[Common props](/docs/react/common-props) > This component is available since `antd@5.0.0`. ### common API | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | icon | Set the icon component of button | ReactNode | - | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | | | content | Text and other | ReactNode | - | | | ~~description~~ | Please use `content` instead | ReactNode | - | | | tooltip | The text shown in the tooltip | ReactNode \| [TooltipProps](/components/tooltip#api) | - | TooltipProps: 5.25.0 | | type | Setting button type | `default` \| `primary` | `default` | | | shape | Setting button shape | `circle` \| `square` | `circle` | | | onClick | Set the handler to handle `click` event | (event) => void | - | | | href | The target of hyperlink | string | - | | | target | Specifies where to display the linked URL | string | - | | | htmlType | Set the original html `type` of `button`, see: [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button#type) | `submit` \| `reset` \| `button` | `button` | 5.21.0 | | badge | Attach Badge to FloatButton. `status` and other props related are not supported. | [BadgeProps](/components/badge#api) | - | 5.4.0 | ### FloatButton.Group | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | open | Whether the menu is visible or not, use it with trigger | boolean | - | | | closeIcon | Customize close button icon | React.ReactNode | `` | | | placement | Customize menu animation placement | `top` \| `left` \| `right` \| `bottom` | `top` | 5.21.0 | | shape | Setting button shape of children | `circle` \| `square` | `circle` | | | styles | Semantic DOM style | [Record](#semantic-dom) | - | | | trigger | Which action can trigger menu open/close | `click` \| `hover` | - | | | onOpenChange | Callback executed when active menu is changed, use it with trigger | (open: boolean) => void | - | | | onClick | Set the handler to handle `click` event (only work in `Menu mode`) | (event) => void | - | 5.3.0 | ### FloatButton.BackTop | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | duration | Time to return to top（ms） | number | 450 | | | target | Specifies the scrollable area dom node | () => HTMLElement | () => window | | | visibilityHeight | The BackTop button will not show until the scroll height reaches this value | number | 400 | | | onClick | A callback function, which can be executed when you click the button | () => void | - | | ## Semantic DOM ### FloatButton ### FloatButton.Group ## Design Token --- Title: Descriptions URL: https://ant.design/components/descriptions --- ## When To Use Commonly displayed on the details page. ```tsx | pure // works when >= 5.8.0, recommended ✅ const items: DescriptionsProps['items'] = [ { key: '1', label: 'UserName', children:

    Zhou Maomao

    , }, { key: '2', label: 'Telephone', children:

    1810000000

    , }, { key: '3', label: 'Live', children:

    Hangzhou, Zhejiang

    , }, { key: '4', label: 'Remark', children:

    empty

    , }, { key: '5', label: 'Address', children:

    No. 18, Wantang Road, Xihu District, Hangzhou, Zhejiang, China

    , }, ]; ; // works when <5.8.0 , deprecated when >=5.8.0 🙅🏻‍♀️ Zhou Maomao 1810000000 Hangzhou, Zhejiang empty No. 18, Wantang Road, Xihu District, Hangzhou, Zhejiang, China ; ``` ## Examples Basic border border padding Custom size responsive Vertical Vertical border Customize label & wrapper style JSX demo Component Token row ## API Common props ref：[Common props](/docs/react/common-props) ### Descriptions | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | bordered | Whether to display the border | boolean | false | | | colon | Change default props `colon` value of Descriptions.Item. Indicates whether the colon after the label is displayed | boolean | true | | | column | The number of `DescriptionItems` in a row, could be an object (like `{ xs: 8, sm: 16, md: 24}`, but must have `bordered={true}`) or a number | number \| [Record](https://github.com/ant-design/ant-design/blob/84ca0d23ae52e4f0940f20b0e22eabe743f90dca/components/descriptions/index.tsx#L111C21-L111C56) | 3 | | | ~~contentStyle~~ | Customize content style, Please use `styles.content` instead | CSSProperties | - | 4.10.0 | | extra | The action area of the description list, placed at the top-right | ReactNode | - | 4.5.0 | | items | Describe the contents of the list item | [DescriptionsItem](#descriptionitem)[] | - | 5.8.0 | | ~~labelStyle~~ | Customize label style | CSSProperties, Please use `styles.label` instead | - | 4.10.0 | | layout | Define description layout | `horizontal` \| `vertical` | `horizontal` | | | size | Set the size of the list. Can be set to `middle`,`small`, or not filled | `default` \| `middle` \| `small` | - | | | title | The title of the description list, placed at the top | ReactNode | - | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.23.0 | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.23.0 | ### DescriptionItem | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | ~~contentStyle~~ | Customize content style, Please use `styles.content` instead | CSSProperties | - | 4.9.0 | | label | The description of the content | ReactNode | - | | | ~~labelStyle~~ | Customize label style, Please use `styles.label` instead | CSSProperties | - | 4.9.0 | | span | The number of columns included(`filled` Fill the remaining part of the current row) | number \| `filled` \| [Screens](/components/grid#col) | 1 | `screens: 5.9.0`, `filled: 5.22.0` | > The number of span Description.Item. Span={2} takes up the width of two DescriptionItems. When both `style` and `labelStyle`(or `contentStyle`) configured, both of them will work. And next one will overwrite first when conflict. ## Semantic DOM ## Design Token --- Title: DatePicker URL: https://ant.design/components/date-picker --- ## When To Use By clicking the input box, you can select a date from a popup calendar. ## Examples Basic Range Picker Multiple Multiple Debug Need Confirm Switchable picker Date Format Choose Time Mask Format Limit Date Range Disabled Disabled Date & Time Allow Empty Select range dates Preset Ranges Extra Footer Three Sizes Customized Cell Rendering Customize Panel External use panel Buddhist Era Status Variants Filled Debug Placement Controlled Panels Customized Range Picker Prefix and Suffix \_InternalPanelDoNotUseOrYouWillBeFired Component Token ## API Common props ref：[Common props](/docs/react/common-props) There are five kinds of picker: - DatePicker - DatePicker\[picker="month"] - DatePicker\[picker="week"] - DatePicker\[picker="year"] - DatePicker\[picker="quarter"] (Added in 4.1.0) - RangePicker ### Localization The default locale is en-US, if you need to use other languages, recommend to use internationalized components provided by us at the entrance. Look at: [ConfigProvider](https://ant.design/components/config-provider/). If there are special needs (only modifying single component language), Please use the property: local. Example: [default](https://github.com/ant-design/ant-design/blob/master/components/date-picker/locale/example.json). ```jsx // The default locale is en-US, if you want to use other locale, just set locale in entry file globally. // Make sure you import the relevant dayjs file as well, otherwise the locale won't change for all texts (e.g. range picker months) import locale from 'antd/locale/zh_CN'; import dayjs from 'dayjs'; import 'dayjs/locale/zh-cn'; dayjs.locale('zh-cn'); ; ``` :::warning When use with Next.js App Router, make sure to add `'use client'` before import locale file of dayjs. It's because all components of Ant Design only works in client, importing locale in RSC will not work. ::: ### Common API The following APIs are shared by DatePicker, RangePicker. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Customize clear button | boolean \| { clearIcon?: ReactNode } | true | 5.8.0: Support object type | | autoFocus | If get focus when component mounted | boolean | false | | | className | The picker className | string | - | | | dateRender | Custom rendering function for date cells, >= 5.4.0 use `cellRender` instead. | function(currentDate: dayjs, today: dayjs) => React.ReactNode | - | < 5.4.0 | | cellRender | Custom rendering function for picker cells | (current: dayjs, info: { originNode: React.ReactElement,today: DateType, range?: 'start' \| 'end', type: PanelMode, locale?: Locale, subType?: 'hour' \| 'minute' \| 'second' \| 'meridiem' }) => React.ReactNode | - | 5.4.0 | | components | Custom panels | Record | - | 5.14.0 | | defaultOpen | Initial open state of picker | boolean | - | | | disabled | Determine whether the DatePicker is disabled | boolean | false | | | disabledDate | Specify the date that cannot be selected | (currentDate: dayjs, info: { from?: dayjs, type: Picker }) => boolean | - | `info`: 5.14.0 | | format | To set the date format, support multi-format matching when it is an array, display the first one shall prevail. refer to [dayjs#format](https://day.js.org/docs/en/display/format). for example: [Custom Format](#date-picker-demo-format) | [formatType](#formattype) | [@rc-component/picker](https://github.com/react-component/picker/blob/f512f18ed59d6791280d1c3d7d37abbb9867eb0b/src/utils/uiUtil.ts#L155-L177) | | | order | Auto order date when multiple or range selection | boolean | true | 5.14.0 | | ~~popupClassName~~ | To customize the className of the popup calendar, use `classNames.popup.root` instead | string | - | 4.23.0 | | preserveInvalidOnBlur | Not clean input on blur even when the typing is invalidate | boolean | false | 5.14.0 | | getPopupContainer | To set the container of the floating layer, while the default is to create a `div` element in `body` | function(trigger) | - | | | inputReadOnly | Set the `readonly` attribute of the input tag (avoids virtual keyboard on touch devices) | boolean | false | | | locale | Localization configuration | object | [default](https://github.com/ant-design/ant-design/blob/master/components/date-picker/locale/example.json) | | | minDate | The minimum date, which also limits the range of panel switching | dayjs | - | 5.14.0 | | maxDate | The maximum date, which also limits the range of panel switching | dayjs | - | 5.14.0 | | mode | The picker panel mode（ [Cannot select year or month anymore?](/docs/react/faq#when-set-mode-to-datepickerrangepicker-cannot-select-year-or-month-anymore) ) | `time` \| `date` \| `month` \| `year` \| `decade` | - | | | needConfirm | Need click confirm button to trigger value change. Default `false` when `multiple` | boolean | - | 5.14.0 | | nextIcon | The custom next icon | ReactNode | - | 4.17.0 | | open | The open state of picker | boolean | - | | | panelRender | Customize panel render | (panelNode) => ReactNode | - | 4.5.0 | | picker | Set picker type | `date` \| `week` \| `month` \| `quarter` \| `year` | `date` | `quarter`: 4.1.0 | | placeholder | The placeholder of date input | string \| \[string,string] | - | | | placement | The position where the selection box pops up | `bottomLeft` `bottomRight` `topLeft` `topRight` | bottomLeft | | | ~~popupStyle~~ | To customize the style of the popup calendar, use `styles.popup.root` instead | CSSProperties | {} | | | prefix | The custom prefix | ReactNode | - | 5.22.0 | | presets | The preset ranges for quick selection, Since `5.8.0`, preset value supports callback function. | { label: React.ReactNode, value: Dayjs \| (() => Dayjs) }\[] | - | | | prevIcon | The custom prev icon | ReactNode | - | 4.17.0 | | size | To determine the size of the input box, the height of `large` and `small`, are 40px and 24px respectively, while default size is 32px | `large` \| `middle` \| `small` | - | | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | style | To customize the style of the input box | CSSProperties | {} | | | suffixIcon | The custom suffix icon | ReactNode | - | | | superNextIcon | The custom super next icon | ReactNode | - | 4.17.0 | | superPrevIcon | The custom super prev icon | ReactNode | - | 4.17.0 | | variant | Variants of picker | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | onOpenChange | Callback function, can be executed whether the popup calendar is popped up or closed | function(open) | - | | | onPanelChange | Callback when picker panel mode is changed | function(value, mode) | - | | ### Common Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ### DatePicker | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | defaultPickerValue | Default panel date, will be reset when panel open | [dayjs](https://day.js.org/) | - | 5.14.0 | | defaultValue | To set default date, if start time or end time is null or undefined, the date range will be an open interval | [dayjs](https://day.js.org/) | - | | | disabledTime | To specify the time that cannot be selected | function(date) | - | | | format | To set the date format. refer to [dayjs#format](https://day.js.org/docs/en/display/format) | [formatType](#formattype) | `YYYY-MM-DD` | | | multiple | Enable multiple selection. Not support `showTime` | boolean | false | 5.14.0 | | pickerValue | Panel date. Used for controlled switching of panel date. Work with `onPanelChange` | [dayjs](https://day.js.org/) | - | 5.14.0 | | renderExtraFooter | Render extra footer in panel | (mode) => React.ReactNode | - | | | showNow | Show the fast access of current datetime | boolean | - | 4.4.0 | | showTime | To provide an additional time selection | object \| boolean | [TimePicker Options](/components/time-picker/#api) | | | showTime.defaultValue | To set default time of selected date, [demo](#date-picker-demo-disabled-date) | [dayjs](https://day.js.org/) | dayjs() | | | showWeek | Show week info when in DatePicker | boolean | false | 5.14.0 | | value | To set date | [dayjs](https://day.js.org/) | - | | | onChange | Callback function, can be executed when the selected time is changing | function(date: dayjs, dateString: string) | - | | | onOk | Callback when click ok button | function() | - | | | onPanelChange | Callback function for panel changing | function(value, mode) | - | | ### DatePicker\[picker=year] | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | defaultValue | To set default date | [dayjs](https://day.js.org/) | - | | | format | To set the date format. refer to [dayjs#format](https://day.js.org/docs/en/display/format) | [formatType](#formattype) | `YYYY` | | | multiple | Enable multiple selection | boolean | false | 5.14.0 | | renderExtraFooter | Render extra footer in panel | () => React.ReactNode | - | | | value | To set date | [dayjs](https://day.js.org/) | - | | | onChange | Callback function, can be executed when the selected time is changing | function(date: dayjs, dateString: string) | - | | ### DatePicker\[picker=quarter] Added in `4.1.0`. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | defaultValue | To set default date | [dayjs](https://day.js.org/) | - | | | format | To set the date format. refer to [dayjs#format](https://day.js.org/docs/en/display/format) | [formatType](#formattype) | `YYYY-\QQ` | | | multiple | Enable multiple selection | boolean | false | 5.14.0 | | renderExtraFooter | Render extra footer in panel | () => React.ReactNode | - | | | value | To set date | [dayjs](https://day.js.org/) | - | | | onChange | Callback function, can be executed when the selected time is changing | function(date: dayjs, dateString: string) | - | | ### DatePicker\[picker=month] | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | defaultValue | To set default date | [dayjs](https://day.js.org/) | - | | | format | To set the date format. refer to [dayjs#format](https://day.js.org/docs/en/display/format) | [formatType](#formattype) | `YYYY-MM` | | | multiple | Enable multiple selection | boolean | false | 5.14.0 | | renderExtraFooter | Render extra footer in panel | () => React.ReactNode | - | | | value | To set date | [dayjs](https://day.js.org/) | - | | | onChange | Callback function, can be executed when the selected time is changing | function(date: dayjs, dateString: string) | - | | ### DatePicker\[picker=week] | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | defaultValue | To set default date | [dayjs](https://day.js.org/) | - | | | format | To set the date format. refer to [dayjs#format](https://day.js.org/docs/en/display/format) | [formatType](#formattype) | `YYYY-wo` | | | multiple | Enable multiple selection | boolean | false | 5.14.0 | | renderExtraFooter | Render extra footer in panel | (mode) => React.ReactNode | - | | | value | To set date | [dayjs](https://day.js.org/) | - | | | onChange | Callback function, can be executed when the selected time is changing | function(date: dayjs, dateString: string) | - | | | showWeek | Show week info when in DatePicker | boolean | true | 5.14.0 | ### RangePicker | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowEmpty | Allow start or end input leave empty | \[boolean, boolean] | \[false, false] | | | cellRender | Custom rendering function for picker cells | (current: dayjs, info: { originNode: React.ReactElement,today: DateType, range?: 'start' \| 'end', type: PanelMode, locale?: Locale, subType?: 'hour' \| 'minute' \| 'second' \| 'meridiem' }) => React.ReactNode | - | 5.4.0 | | dateRender | Custom rendering function for date cells, >= 5.4.0 use `cellRender` instead. | function(currentDate: dayjs, today: dayjs) => React.ReactNode | - | < 5.4.0 | | defaultPickerValue | Default panel date, will be reset when panel open | [dayjs](https://day.js.org/) | - | 5.14.0 | | defaultValue | To set default date | \[[dayjs](https://day.js.org/), [dayjs](https://day.js.org/)] | - | | | disabled | If disable start or end | \[boolean, boolean] | - | | | disabledTime | To specify the time that cannot be selected | function(date: dayjs, partial: `start` \| `end`, info: { from?: dayjs }) | - | `info.from`: 5.17.0 | | format | To set the date format. refer to [dayjs#format](https://day.js.org/docs/en/display/format) | [formatType](#formattype) | `YYYY-MM-DD HH:mm:ss` | | | id | Config input ids | { start?: string, end?: string } | - | 5.14.0 | | pickerValue | Panel date. Used for controlled switching of panel date. Work with `onPanelChange` | [dayjs](https://day.js.org/) | - | 5.14.0 | | presets | The preset ranges for quick selection, Since `5.8.0`, preset value supports callback function. | { label: React.ReactNode, value: (Dayjs \| (() => Dayjs))\[] }\[] | - | | | renderExtraFooter | Render extra footer in panel | () => React.ReactNode | - | | | separator | Set separator between inputs | React.ReactNode | `` | | | showTime | To provide an additional time selection | object \| boolean | [TimePicker Options](/components/time-picker/#api) | | | showTime.defaultValue | To set default time of selected date, [demo](#date-picker-demo-disabled-date) | [dayjs](https://day.js.org/)\[] | \[dayjs(), dayjs()] | | | value | To set date | \[[dayjs](https://day.js.org/), [dayjs](https://day.js.org/)] | - | | | onCalendarChange | Callback function, can be executed when the start time or the end time of the range is changing. `info` argument is added in 4.4.0 | function(dates: \[dayjs, dayjs], dateStrings: \[string, string], info: { range:`start`\|`end` }) | - | | | onChange | Callback function, can be executed when the selected time is changing | function(dates: \[dayjs, dayjs], dateStrings: \[string, string]) | - | | | onFocus | Trigger when get focus | function(event, { range: 'start' \| 'end' }) | - | `range`: 5.14.0 | | onBlur | Trigger when lose focus | function(event, { range: 'start' \| 'end' }) | - | `range`: 5.14.0 | #### formatType ```typescript import type { Dayjs } from 'dayjs'; type Generic = string; type GenericFn = (value: Dayjs) => string; export type FormatType = | Generic | GenericFn | Array | { format: string; type?: 'mask'; }; ``` Note: `type` is added in `5.14.0`. ## Semantic DOM ## Design Token ## FAQ ### When set mode to DatePicker/RangePicker, cannot select year or month anymore? Please refer [FAQ](/docs/react/faq#when-set-mode-to-datepickerrangepicker-cannot-select-year-or-month-anymore) ### Why does the date picker switch to the date panel after selecting the year instead of the month panel? After selecting the year, the system directly switches to the date panel instead of month panel. This design is intended to reduce the user's operational burden by allowing them to complete the year modification with just one click, without having to enter the month selection interface again. At the same time, it also avoids additional cognitive burden of remembering the month. ### How to use DatePicker with customize date library like dayjs? Please refer [Use custom date library](/docs/react/use-custom-date-library#datepicker) ### Why config dayjs.locale globally not work? DatePicker default set `locale` as `en` in v4. You can config DatePicker `locale` prop or [ConfigProvider `locale`](/components/config-provider) prop instead. #### Date-related components locale is not working? See FAQ [Date-related-components-locale-is-not-working?](/docs/react/faq#date-related-components-locale-is-not-working) ### How to modify start day of week? Please use correct [language](/docs/react/i18n) ([#5605](https://github.com/ant-design/ant-design/issues/5605)), or update dayjs `locale` config: - Example: ```js import dayjs from 'dayjs'; import 'dayjs/locale/zh-cn'; import updateLocale from 'dayjs/plugin/updateLocale'; dayjs.extend(updateLocale); dayjs.updateLocale('zh-cn', { weekStart: 0, }); ``` ### Why origin panel don't switch when using `panelRender`? When you change the layout of nodes by `panelRender`, React will unmount and re-mount it which reset the component state. You should keep the layout stable. Please ref [#27263](https://github.com/ant-design/ant-design/issues/27263) for more info. ### How to understand disabled time and date? Please refer to the blog ['Why is it so hard to disable the date?'](/docs/blog/picker), to learn how to use it. --- Title: Collapse URL: https://ant.design/components/collapse --- ## When To Use - Can be used to group or hide complex regions to keep the page clean. - `Accordion` is a special kind of `Collapse`, which allows only one panel to be expanded at a time. ```tsx | pure // works when >= 5.6.0, recommended ✅ const text = ` A dog is a type of domesticated animal. Known for its loyalty and faithfulness, it can be found as a welcome guest in many households across the world. `; const items: CollapseProps['items'] = [ { key: '1', label: 'This is panel header 1', children:

    {text}

    , }, { key: '2', label: 'This is panel header 2', children:

    {text}

    , }, { key: '3', label: 'This is panel header 3', children:

    {text}

    , }, ]; ; // works when <5.6.0 , deprecated when >=5.6.0 🙅🏻‍♀️

    {text}

    {text}

    {text}

         ; ``` ## Examples Collapse Size Accordion Nested panel Borderless Custom Panel No arrow Extra node Ghost Collapse Collapsible Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Collapse | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | accordion | If true, Collapse renders as Accordion | boolean | false | | | activeKey | Key of the active panel | string\[] \| string
    number\[] \| number | No default value. In [accordion mode](#collapse-demo-accordion), it's the key of the first panel | | | bordered | Toggles rendering of the border around the collapse block | boolean | true | | | collapsible | Specify how to trigger Collapse. Either by clicking icon or by clicking any area in header or disable collapse functionality itself | `header` \| `icon` \| `disabled` | - | 4.9.0 | | defaultActiveKey | Key of the initial active panel | string\[] \| string
    number\[] \| number | - | | | ~~destroyInactivePanel~~ | Destroy Inactive Panel | boolean | false | | | destroyOnHidden | Destroy Inactive Panel | boolean | false | 5.25.0 | | expandIcon | Allow to customize collapse icon | (panelProps) => ReactNode | - | | | expandIconPlacement | Set expand icon placement | `start` \| `end` | `start` | - | | ~~expandIconPosition~~ | Set expand icon position, Please use `expandIconPlacement` instead | `start` \| `end` | - | 4.21.0 | | ghost | Make the collapse borderless and its background transparent | boolean | false | 4.4.0 | | size | Set the size of collapse | `large` \| `middle` \| `small` | `middle` | 5.2.0 | | onChange | Callback function executed when active panel is changed | function | - | | | items | collapse items content | [ItemType](#itemtype) | - | 5.6.0 | ### ItemType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | classNames | Semantic structure className | [`Record
    `](#semantic-dom) | - | 5.21.0 | | collapsible | Specify whether the panel be collapsible or the trigger area of collapsible | `header` \| `icon` \| `disabled` | - | | | children | Body area content | ReactNode | - | | | extra | The extra element in the corner | ReactNode | - | | | forceRender | Forced render of content on panel, instead of lazy rendering after clicking on header | boolean | false | | | key | Unique key identifying the panel from among its siblings | string \| number | - | | | label | Title of the panel | ReactNode | - | - | | showArrow | If false, panel will not show arrow icon. If false, collapsible can't be set as icon | boolean | true | | | styles | Semantic DOM style | [`Record
    `](#semantic-dom) | - | 5.21.0 | ### Collapse.Panel :::warning{title=Deprecated} When using version >= 5.6.0, we prefer to configuring the panel by `items`. ::: | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | collapsible | Specify whether the panel be collapsible or the trigger area of collapsible | `header` \| `icon` \| `disabled` | - | 4.9.0 (icon: 4.24.0) | | extra | The extra element in the corner | ReactNode | - | | | forceRender | Forced render of content on panel, instead of lazy rendering after clicking on header | boolean | false | | | header | Title of the panel | ReactNode | - | | | key | Unique key identifying the panel from among its siblings | string \| number | - | | | showArrow | If false, panel will not show arrow icon. If false, collapsible can't be set as icon | boolean | true | | ## Semantic DOM ## Design Token --- Title: ConfigProvider URL: https://ant.design/components/config-provider --- ## Usage This component provides a configuration to all React components underneath itself via the [context API](https://react.dev/learn/passing-data-deeply-with-context). In the render tree all components will have access to the provided config. ```tsx import React from 'react'; import { ConfigProvider } from 'antd'; // ... const Demo: React.FC = () => ( ); export default Demo; ``` ### Content Security Policy {#csp} Some components use dynamic style to support wave effect. You can config `csp` prop if Content Security Policy (CSP) is enabled: ```tsx ``` ## Examples Locale Direction Component size Theme Custom Wave Static function prefixCls useConfig warning ## API | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | componentDisabled | Config antd component `disabled` | boolean | - | 4.21.0 | | componentSize | Config antd component size | `small` \| `middle` \| `large` | - | | | csp | Set [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) config | { nonce: string } | - | | | direction | Set direction of layout. See [demo](#config-provider-demo-direction) | `ltr` \| `rtl` | `ltr` | | | getPopupContainer | To set the container of the popup element. The default is to create a `div` element in `body` | function(triggerNode) | () => document.body | | | getTargetContainer | Config Affix, Anchor scroll target container | () => HTMLElement | () => window | 4.2.0 | | iconPrefixCls | Set icon prefix className | string | `anticon` | 4.11.0 | | locale | Language package setting, you can find the packages in [antd/locale](http://unpkg.com/antd/locale/) | object | - | | | popupMatchSelectWidth | Determine whether the dropdown menu and the select input are the same width. Default set `min-width` same as input. Will ignore when value less than select width. `false` will disable virtual scroll | boolean \| number | - | 5.5.0 | | popupOverflow | Select like component popup logic. Can set to show in viewport or follow window scroll | 'viewport' \| 'scroll' | 'viewport' | 5.5.0 | | prefixCls | Set prefix className | string | `ant` | | | renderEmpty | Set empty content of components. Ref [Empty](/components/empty/) | function(componentName: string): ReactNode | - | | | theme | Set theme, ref [Customize Theme](/docs/react/customize-theme) | [Theme](/docs/react/customize-theme#theme) | - | 5.0.0 | | variant | Set variant of data entry components | `outlined` \| `filled` \| `borderless` | - | 5.19.0 | | virtual | Disable virtual scroll when set to `false` | boolean | - | 4.3.0 | | warning | Config warning level, when `strict` is `false`, it will aggregate deprecated information into a single message | { strict: boolean } | - | 5.10.0 | ### ConfigProvider.config() {#config} Setting `Modal`, `Message`, `Notification` static config. Not work on hooks. ```tsx ConfigProvider.config({ // 5.13.0+ holderRender: (children) => ( {children} ), }); ``` ### ConfigProvider.useConfig() 5.3.0+ {#useconfig} Get the value of the parent `Provider`, Such as `DisabledContextProvider`, `SizeContextProvider`. ```jsx const { componentDisabled, // 5.3.0+ componentSize, // 5.3.0+ } = ConfigProvider.useConfig(); ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | componentDisabled | antd component disabled state | boolean | - | 5.3.0 | | componentSize | antd component size state | `small` \| `middle` \| `large` | - | 5.3.0 | ### Component Config | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | affix | Set Affix common props | { className?: string, style?: React.CSSProperties } | - | 6.0.0 | | alert | Set Alert common props | { className?: string, style?: React.CSSProperties, closeIcon?: React.ReactNode } | - | 5.7.0, `closeIcon`: 5.14.0 | | anchor | Set Anchor common props | { className?: string, style?: React.CSSProperties, classNames?: [AnchorStyleConfig\["classNames"\]](/components/anchor#semantic-dom), styles?: [AnchorStyleConfig\["styles"\]](/components/anchor#semantic-dom) } | - | 5.7.0 , `classNames` and `styles`: 6.0.0 | | avatar | Set Avatar common props | { className?: string, style?: React.CSSProperties } | - | 5.7.0 | | badge | Set Badge common props | { className?: string, style?: React.CSSProperties, classNames?: [BadgeProps\["classNames"\]](/components/badge#semantic-dom), styles?: [BadgeProps\["styles"\]](/components/badge#semantic-dom) } | - | 5.7.0 | | breadcrumb | Set Breadcrumb common props | { className?: string, style?: React.CSSProperties, classNames?: [BreadcrumbConfig\["classNames"\]](/components/breadcrumb#semantic-dom), styles?: [BreadcrumbConfig\["styles"\]](/components/breadcrumb#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | button | Set Button common props | { className?: string, style?: React.CSSProperties, classNames?: [ButtonProps\["classNames"\]](/components/button#semantic-dom), styles?: [ButtonProps\["styles"\]](/components/button#semantic-dom), autoInsertSpace?: boolean, variant?: ButtonVariantType, color?: ButtonColorType, shape?: [ButtonProps\["shape"\]](/components/button#api) } | - | 5.6.0, `autoInsertSpace`: 5.17.0, `variant` and `color`: 5.25.0, `shape`: 5.27.0 | | card | Set Card common props | { className?: string, style?: React.CSSProperties, classNames?: [CardProps\["classNames"\]](/components/card#semantic-dom), styles?: [CardProps\["styles"\]](/components/card#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 5.14.0 | | cardMeta | Set Card.Meta common props | { className?: string, style?: React.CSSProperties, classNames?: [CardMetaProps\["classNames"\]](/components/card#semantic-dom), styles?: [CardMetaProps\["styles"\]](/components/card#semantic-dom) } | - | 6.0.0 | | calendar | Set Calendar common props | { className?: string, style?: React.CSSProperties, classNames?: [CalendarConfig\["classNames"\]](/components/calendar#semantic-dom), styles?: [CalendarConfig\["styles"\]](/components/calendar#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | carousel | Set Carousel common props | { className?: string, style?: React.CSSProperties } | - | 5.7.0 | | cascader | Set Cascader common props | { className?: string, style?: React.CSSProperties } | - | 5.7.0 | | checkbox | Set Checkbox common props | { className?: string, style?: React.CSSProperties, classNames?: [CheckboxConfig\["classNames"\]](/components/checkbox#semantic-dom), styles?: [CheckboxConfig\["styles"\]](/components/checkbox#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | collapse | Set Collapse common props | { className?: string, style?: React.CSSProperties, expandIcon?: (props) => ReactNode, classNames?: [CollapseProps\["classNames"\]](/components/collapse#semantic-dom), styles?: [CollapseProps\["styles"\]](/components/collapse#semantic-dom) } | - | 5.7.0, `expandIcon`: 5.15.0, `classNames` and `styles`: 6.0.0 | | colorPicker | Set ColorPicker common props | { className?: string, style?: React.CSSProperties, classNames?: [ColorPickerConfig\["classNames"\]](/components/color-picker#semantic-dom), styles?: [ColorPickerConfig\["styles"\]](/components/color-picker#semantic-dom) } | - | 5.7.0 | | datePicker | Set datePicker common props | { className?: string, style?: React.CSSProperties, classNames?: [DatePickerConfig\["classNames"\]](/components/date-picker#semantic-dom), styles?: [DatePickerConfig\["styles"\]](/components/date-picker#semantic-dom) } | - | 5.7.0 | | rangePicker | Set rangePicker common props | { className?: string, style?: React.CSSProperties } | - | 5.11.0 | | descriptions | Set Descriptions common props | { className?: string, style?: React.CSSProperties, classNames?: [DescriptionsProps\["classNames"\]](/components/descriptions#semantic-dom), styles?: [DescriptionsProps\["styles"\]](/components/descriptions#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 5.23.0 | | divider | Set Divider common props | { className?: string, style?: React.CSSProperties, classNames?: [DividerProps\["classNames"\]](/components/divider#semantic-dom), styles?: [DividerProps\["styles"\]](/components/divider#semantic-dom) } | - | | | drawer | Set Drawer common props | { className?: string, style?: React.CSSProperties, classNames?: [DrawerProps\["classNames"\]](/components/drawer#semantic-dom), styles?: [DrawerProps\["styles"\]](/components/drawer#semantic-dom), closeIcon?: ReactNode } | - | 5.7.0, `classNames` and `styles`: 5.10.0, `closeIcon`: 5.14.0 | | dropdown | Set Dropdown common props | { className?: string, style?: React.CSSProperties, classNames?: [DropdownConfig\["classNames"\]](/components/dropdown#semantic-dom), styles?: [DropdownConfig\["styles"\]](/components/dropdown#semantic-dom) } | - | | | empty | Set Empty common props | { className?: string, style?: React.CSSProperties, classNames?: [EmptyProps\["classNames"\]](/components/empty#semantic-dom), styles?: [EmptyProps\["styles"\]](/components/empty#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 5.23.0 | | flex | Set Flex common props | { className?: string, style?: React.CSSProperties, vertical?: boolean } | - | 5.10.0 | | floatButton | Set FloatButton common props | { className?: string, style?: React.CSSProperties, classNames?: [FloatButtonProps\["classNames"\]](/components/float-button#semantic-dom), styles?: [FloatButtonProps\["styles"\]](/components/float-button#semantic-dom) } | - | | | floatButtonGroup | Set FloatButton.Group common props | { closeIcon?: React.ReactNode, className?: string, style?: React.CSSProperties, classNames?: [FloatButtonProps\["classNames"\]](/components/float-button#semantic-dom), styles?: [FloatButtonProps\["styles"\]](/components/float-button#semantic-dom) } | - | | | form | Set Form common props | { className?: string, style?: React.CSSProperties, validateMessages?: [ValidateMessages](/components/form/#validatemessages), requiredMark?: boolean \| `optional`, scrollToFirstError?: boolean \| [Options](https://github.com/stipsan/scroll-into-view-if-needed/tree/ece40bd9143f48caf4b99503425ecb16b0ad8249#options), classNames?:[FormConfig\["classNames"\]](/components/form#semantic-dom), styles?: [FormConfig\["styles"\]](/components/form#semantic-dom) } | - | `requiredMark`: 4.8.0; `colon`: 4.18.0; `scrollToFirstError`: 5.2.0; `className` and `style`: 5.7.0 | | image | Set Image common props | { className?: string, style?: React.CSSProperties, preview?: { closeIcon?: React.ReactNode, classNames?:[ImageConfig\["classNames"\]](/components/image#semantic-dom), styles?: [ImageConfig\["styles"\]](/components/image#semantic-dom) } } | - | 5.7.0, `closeIcon`: 5.14.0, `classNames` and `styles`: 6.0.0 | | input | Set Input common props | { autoComplete?: string, className?: string, style?: React.CSSProperties, allowClear?: boolean \| { clearIcon?: ReactNode } } | - | 4.2.0, `allowClear`: 5.15.0 | | inputNumber | Set InputNumber common props | { className?: string, style?: React.CSSProperties, classNames?: [InputNumberConfig\["classNames"\]](/components/input-number#semantic-dom), styles?: [InputNumberConfig\["styles"\]](/components/input-number#semantic-dom) } | - | | | otp | Set OTP common props | { className?: string, style?: React.CSSProperties, classNames?: [OTPConfig\["classNames"\]](/components/input#semantic-otp), styles?: [OTPConfig\["styles"\]](/components/input#semantic-otp) } | - | | | inputSearch | Set Search common props | { className?: string, style?: React.CSSProperties, classNames?: [InputSearchConfig\["classNames"\]](/components/input#semantic-search), styles?: [InputSearchConfig\["styles"\]](/components/input#semantic-search) } | - | | | textArea | Set TextArea common props | { autoComplete?: string, className?: string, style?: React.CSSProperties,classNames?:[TextAreaConfig\["classNames"\]](/components/input#semantic-textarea), styles?: [TextAreaConfig\["styles"\]](/components/input#semantic-textarea), allowClear?: boolean \| { clearIcon?: ReactNode } } | - | 5.15.0 | | layout | Set Layout common props | { className?: string, style?: React.CSSProperties } | - | 5.7.0 | | list | Set List common props | { className?: string, style?: React.CSSProperties, item?:{ classNames: [ListItemProps\["classNames"\]](/components/list#listitem), styles: [ListItemProps\["styles"\]](/components/list#listitem) } } | - | 5.7.0 | | masonry | Set Masonry common props | { className?: string, style?: React.CSSProperties, classNames?: [MasonryProps\["classNames"\]](/components/masonry#semantic-dom), styles?: [MasonryProps\["styles"\]](/components/masonry#semantic-dom) } | - | | | menu | Set Menu common props | { className?: string, style?: React.CSSProperties, expandIcon?: ReactNode \| props => ReactNode } | - | 5.7.0, `expandIcon`: 5.15.0 | | mentions | Set Mentions common props | { className?: string, style?: React.CSSProperties, classNames?:[MentionsConfig\["classNames"\]](/components/mentions#semantic-dom), styles?: [MentionsConfig\["styles"\]](/components/mentions#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | message | Set Message common props | { className?: string, style?: React.CSSProperties, classNames?: [MessageConfig\["classNames"\]](/components/message#semantic-dom), styles?: [MessageConfig\["styles"\]](/components/message#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | modal | Set Modal common props | { className?: string, style?: React.CSSProperties, classNames?: [ModalProps\["classNames"\]](/components/modal#semantic-dom), styles?: [ModalProps\["styles"\]](/components/modal#semantic-dom), closeIcon?: React.ReactNode } | - | 5.7.0, `classNames` and `styles`: 5.10.0, `closeIcon`: 5.14.0 | | notification | Set Notification common props | { className?: string, style?: React.CSSProperties, closeIcon?: React.ReactNode, classNames?: [NotificationConfig\["classNames"\]](/components/notification#semantic-dom), styles?: [NotificationConfig\["styles"\]](/components/notification#semantic-dom) } | - | 5.7.0, `closeIcon`: 5.14.0, `classNames` and `styles`: 6.0.0 | | pagination | Set Pagination common props | { showSizeChanger?: boolean, className?: string, style?: React.CSSProperties,classNames?:[PaginationConfig\["classNames"\]](/components/pagination#semantic-dom), styles?: [PaginationConfig\["styles"\]](/components/pagination#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | progress | Set Progress common props | { className?: string, style?: React.CSSProperties, classNames?: [ProgressConfig\["classNames"\]](/components/progress#semantic-dom), styles?: [ProgressConfig\["styles"\]](/components/progress#semantic-dom) } | - | | | radio | Set Radio common props | { className?: string, style?: React.CSSProperties, classNames?: [RadioConfig\["classNames"\]](/components/radio#semantic-dom), styles?: [RadioConfig\["styles"\]](/components/radio#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | rate | Set Rate common props | { className?: string, style?: React.CSSProperties } | - | 5.7.0 | | result | Set Result common props | { className?: string, style?: React.CSSProperties , classNames?: [ResultProps\["classNames"\]](/components/result#semantic-dom), styles?: [ResultProps\["styles"\]](/components/result#semantic-dom)} | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | ribbon | Set Ribbon common props | { className?: string, style?: React.CSSProperties, , classNames?: [RibbonProps\["classNames"\]](/components/badge#semantic-dom), styles?: [RibbonProps\["styles"\]](/components/badge#semantic-dom) } | - | 6.0.0 | | skeleton | Set Skeleton common props | { className?: string, style?: React.CSSProperties, classNames?: [SkeletonProps\["classNames"\]](/components/skeleton#semantic-dom), styles?: [SkeletonProps\["styles"\]](/components/skeleton#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | segmented | Set Segmented common props | { className?: string, style?: React.CSSProperties, classNames?: [SegmentedProps\["classNames"\]](/components/segmented#semantic-dom), styles?: [SegmentedProps\["styles"\]](/components/segmented#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | select | Set Select common props | { className?: string, showSearch?: boolean, style?: React.CSSProperties, classNames?: [SelectConfig\["classNames"\]](/components/select#semantic-dom), styles?: [SelectConfig\["styles"\]](/components/select#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | slider | Set Slider common props | { className?: string, style?: React.CSSProperties, classNames?: [SliderProps\["classNames"\]](/components/slider#semantic-dom), styles?: [SliderProps\["styles"\]](/components/slider#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 5.23.0 | | switch | Set Switch common props | { className?: string, style?: React.CSSProperties, classNames?: [SwitchStyleConfig\["classNames"\]](/components/switch#semantic-dom), styles?: [SwitchStyleConfig\["styles"\]](/components/switch#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | space | Set Space common props, ref [Space](/components/space) | { size: `small` \| `middle` \| `large` \| `number`, className?: string, style?: React.CSSProperties, classNames?: [SpaceProps\["classNames"\]](/components/space#semantic-dom), styles?: [SpaceProps\["styles"\]](/components/space#semantic-dom) } | - | 5.6.0 | | splitter | Set Splitter common props | { className?: string, style?: React.CSSProperties, classNames?:[Splitter\["classNames"\]](/components/splitter#semantic-dom), styles?: [Splitter\["styles"\]](/components/splitter#semantic-dom) } | - | 5.21.0 | | spin | Set Spin common props | { className?: string, style?: React.CSSProperties, indicator?: React.ReactElement, classNames?:[SpinConfig\["classNames"\]](/components/spin#semantic-dom), styles?: [SpinConfig\["styles"\]](/components/spin#semantic-dom) } | - | 5.7.0, `indicator`: 5.20.0, `classNames` and `styles`: 6.0.0 | | statistic | Set Statistic common props | { className?: string, style?: React.CSSProperties, classNames?: [StatisticProps\["classNames"\]](/components/statistic#semantic-dom), styles?: [StatisticProps\["styles"\]](/components/statistic#semantic-dom)} | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | steps | Set Steps common props | { className?: string, style?: React.CSSProperties, classNames?:[StepsConfig\["classNames"\]](/components/steps#semantic-dom), styles?: [StepsConfig\["styles"\]](/components/steps#semantic-dom) } | - | | | table | Set Table common props | { className?: string, style?: React.CSSProperties, expandable?: { expandIcon?: props => React.ReactNode }, classNames?: [TableProps\["classNames"\]](/components/table#semantic-dom), styles?: [TableProps\["styles"\]](/components/table#semantic-dom) } | - | | | tabs | Set Tabs common props | { className?: string, style?: React.CSSProperties, indicator?: { size?: GetIndicatorSize, align?: `start` \| `center` \| `end` }, moreIcon?: ReactNode, addIcon?: ReactNode, removeIcon?: ReactNode, classNames?: [TabsConfig\["classNames"\]](/components/tabs#semantic-dom), styles?: [TabsConfig\["styles"\]](/components/tabs#semantic-dom) } | - | 5.7.0, `moreIcon` and `addIcon`: 5.14.0, `removeIcon`: 5.15.0, `classNames` and `styles`: 6.0.0 | | tag | Set Tag common props | { className?: string, style?: React.CSSProperties, closeIcon?: React.ReactNode, classNames?: [TagProps\["classNames"\]](/components/tag#semantic-dom), styles?: [TagProps\["styles"\]](/components/tag#semantic-dom) } | - | 5.7.0, `closeIcon`: 5.14.0, `classNames` and `styles`: 6.0.0 | | timeline | Set Timeline common props | { className?: string, style?: React.CSSProperties, classNames?: [TimelineConfig\["classNames"\]](/components/timeline#semantic-dom), styles?: [TimelineConfig\["styles"\]](/components/timeline#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | timePicker | Set TimePicker common props | { className?: string, style?: React.CSSProperties, classNames?: [TimePickerConfig\["classNames"\]](/components/time-picker#semantic-dom), styles?: [TimePickerConfig\["styles"\]](/components/time-picker#semantic-dom) } | - | 5.7.0 | | tour | Set Tour common props | { closeIcon?: React.ReactNode, className?: string, style?: React.CSSProperties, classNames?: [TourProps\["classNames"\]](/components/tour#semantic-dom), styles?: [TourProps\["styles"\]](/components/tour#semantic-dom) } | - | 5.14.0, `classNames`、`styles`、`className`、`style`: 6.0.0 | | tooltip | Set Tooltip common props | { className?: string, style?: React.CSSProperties, classNames?:[Tooltip\["classNames"\]](/components/tooltip#semantic-dom), styles?: [Tooltip\["styles"\]](/components/tooltip#semantic-dom), arrow: boolean \| { pointAtCenter: boolean } } | - | 5.23.0, `arrow`: 6.0.0 | | popover | Set Popover common props | { className?: string, style?: React.CSSProperties, classNames?:[Popover\["classNames"\]](/components/popover#semantic-dom), styles?: [Popover\["styles"\]](/components/popover#semantic-dom), arrow: boolean \| { pointAtCenter: boolean } } | - | 5.23.0, `arrow`: 6.0.0 | | popconfirm | Set Popconfirm common props | { className?: string, style?: React.CSSProperties, classNames?:[Popconfirm\["classNames"\]](/components/popconfirm#semantic-dom), styles?: [Popconfirm\["styles"\]](/components/popconfirm#semantic-dom), arrow: boolean \| { pointAtCenter: boolean } } | - | 5.23.0, `arrow`: 6.0.0 | | qrcode | Set QRCode common props | { className?: string, style?: React.CSSProperties, classNames?:[QRCode\["classNames"\]](/components/qr-code#semantic-dom), styles?: [QRCode\["styles"\]](/components/qr-code#semantic-dom) } | - | | | transfer | Set Transfer common props | { className?: string, style?: React.CSSProperties, classNames?: [TransferConfig\["classNames"\]](/components/transfer#semantic-dom), styles?: [TransferConfig\["styles"\]](/components/transfer#semantic-dom), selectionsIcon?: React.ReactNode } | - | | | tree | Set Tree common props | { className?: string, style?: React.CSSProperties, classNames?: [TreeConfig\["classNames"\]](/components/tree#semantic-dom), styles?: [TreeConfig\["styles"\]](/components/tree#semantic-dom) } | - | 5.7.0, `classNames` and `styles`: 6.0.0 | | treeSelect | Set TreeSelect common props | { className?: string, style?: React.CSSProperties, classNames?: [TreeSelectConfig\["classNames"\]](/components/tree-select#semantic-dom), styles?: [TreeSelectConfig\["styles"\]](/components/tree-select#semantic-dom) } | - | | | typography | Set Typography common props | { className?: string, style?: React.CSSProperties } | - | 5.7.0 | | upload | Set Upload common props | { className?: string, style?: React.CSSProperties, classNames?:[UploadConfig\["classNames"\]](/components/upload#semantic-dom), styles?: [UploadConfig\["styles"\]](/components/upload#semantic-dom), customRequest?: [Upload\["customRequest"\]](/components/upload#api) } | - | 5.7.0, `customRequest`: 5.27.0, `classNames` and `styles`: 6.0.0 | | wave | Config wave effect | { disabled?: boolean, showEffect?: (node: HTMLElement, info: { className, token, component }) => void } | - | 5.8.0 | ## FAQ ### How to contribute a new language? {#faq-add-locale} See [<Adding new language>](/docs/react/i18n#adding-newplanguage). ### Date-related components locale is not working? {#faq-locale-not-work} See FAQ [Date-related-components-locale-is-not-working?](/docs/react/faq#date-related-components-locale-is-not-working) ### Modal throw error when setting `getPopupContainer`? {#faq-get-popup-container} Related issue: When you config `getPopupContainer` to parentNode globally, Modal will throw error of `triggerNode is undefined` because it did not have a triggerNode. You can try the [fix](https://github.com/afc163/feedback-antd/commit/3e4d1ad1bc1a38460dc3bf3c56517f737fe7d44a) below. ```diff triggerNode.parentNode} + getPopupContainer={node => { + if (node) { + return node.parentNode; + } + return document.body; + }} > ``` ### Why can't ConfigProvider props (like `prefixCls` and `theme`) affect ReactNode inside `message.info`, `notification.open`, `Modal.confirm`? {#faq-message-inherit} antd will dynamic create React instance by `ReactDOM.render` when call message methods. Whose context is different with origin code located context. We recommend `useMessage`, `useNotification` and `useModal` which , the methods came from `message/notification/Modal` has been deprecated in 5.x. ### Locale is not working with Vite in production mode? {#faq-vite-locale-not-work} Related issue: [#39045](https://github.com/ant-design/ant-design/issues/39045) In production mode of Vite, default exports from cjs file should be used like this: `enUS.default`. So you can directly import locale from `es/` directory like `import enUS from 'antd/es/locale/en_US'` to make dev and production have the same behavior. ### `prefixCls` priority(The former is covered by the latter) {#faq-prefixcls-priority} 1. `ConfigProvider.config({ prefixCls: 'prefix-1' })` 2. `ConfigProvider.config({ holderRender: (children) => {children} })` 3. `message.config({ prefixCls: 'prefix-3' })` --- Title: ColorPicker URL: https://ant.design/components/color-picker --- ## When To Use Used when the user needs to make a customized color selection. ## Examples Basic Usage Trigger size controlled mode Line Gradient Rendering Trigger Text Disable Disabled Alpha Clear Color Custom Trigger Custom Trigger Event Color Format Preset Colors Preset Line Gradient Custom Render Panel Pure Render ## API Common props ref：[Common props](/docs/react/common-props) > This component is available since `antd@5.5.0`. | Property | Description | Type | Default | Version | | :-- | :-- | :-- | :-- | :-- | | allowClear | Allow clearing color selected | boolean | false | | | arrow | Configuration for popup arrow | `boolean \| { pointAtCenter: boolean }` | true | | | children | Trigger of ColorPicker | React.ReactNode | - | | | defaultValue | Default value of color | [ColorType](#colortype) | - | | | defaultFormat | Default format of color | `rgb` \| `hex` \| `hsb` | `hex` | 5.9.0 | | disabled | Disable ColorPicker | boolean | - | | | disabledAlpha | Disable Alpha | boolean | - | 5.8.0 | | disabledFormat | Disable format of color | boolean | - | | | ~~destroyTooltipOnHide~~ | Whether destroy dom when close | `boolean` | false | 5.7.0 | | destroyOnHidden | Whether destroy dom when close | `boolean` | false | 5.25.0 | | format | Format of color | `rgb` \| `hex` \| `hsb` | - | | | mode | Configure single or gradient color | `'single' \| 'gradient' \| ('single' \| 'gradient')[]` | `single` | 5.20.0 | | open | Whether to show popup | boolean | - | | | presets | Preset colors | [PresetColorType](#presetcolortype) | - | | | placement | Placement of popup | The design of the [placement](/components/tooltip/#api) parameter is the same as the `Tooltips` component. | `bottomLeft` | | | panelRender | Custom Render Panel | `(panel: React.ReactNode, extra: { components: { Picker: FC; Presets: FC } }) => React.ReactNode` | - | 5.7.0 | | showText | Show color text | boolean \| `(color: Color) => React.ReactNode` | - | 5.7.0 | | size | Setting the trigger size | `large` \| `middle` \| `small` | `middle` | 5.7.0 | | trigger | ColorPicker trigger mode | `hover` \| `click` | `click` | | | value | Value of color | [ColorType](#colortype) | - | | | onChange | Callback when `value` is changed | `(value: Color, css: string) => void` | - | | | onChangeComplete | Called when color pick ends. Will not change the display color when `value` controlled by `onChangeComplete` | `(value: Color) => void` | - | 5.7.0 | | onFormatChange | Callback when `format` is changed | `(format: 'hex' \| 'rgb' \| 'hsb') => void` | - | | | onOpenChange | Callback when `open` is changed | `(open: boolean) => void` | - | | | onClear | Called when clear | `() => void` | - | 5.6.0 | #### ColorType ```typescript type ColorType = | string | Color | { color: string; percent: number; }[]; ``` #### PresetColorType ```typescript type PresetColorType = { label: React.ReactNode; defaultOpen?: boolean; key?: React.Key; colors: ColorType[]; }; ``` ### Color | Property | Description | Type | Version | | :-- | :-- | :-- | :-- | | toCssString | Convert to CSS support format | `() => string` | 5.20.0 | | toHex | Convert to `hex` format characters, the return type like: `1677ff` | `() => string` | - | | toHexString | Convert to `hex` format color string, the return type like: `#1677ff` | `() => string` | - | | toHsb | Convert to `hsb` object | `() => ({ h: number, s: number, b: number, a number })` | - | | toHsbString | Convert to `hsb` format color string, the return type like: `hsb(215, 91%, 100%)` | `() => string` | - | | toRgb | Convert to `rgb` object | `() => ({ r: number, g: number, b: number, a number })` | - | | toRgbString | Convert to `rgb` format color string, the return type like: `rgb(22, 119, 255)` | `() => string` | - | ## Semantic DOM ## FAQ ### Questions about color assignment The value of the color selector supports both string color values and selector-generated `Color` objects. However, since there is a precision error when converting color strings of different formats to each other, it is recommended to use selector-generated `Color` objects for assignment operations in controlled scenarios, so that the precision problem can be avoided and the values are guaranteed to be accurate and the selector can work as expected. --- Title: Empty URL: https://ant.design/components/empty --- ## When To Use - When there is no data provided, display for friendly tips. - User tutorial to create something in fresh new situation. ## Examples Basic Choose image Customize ConfigProvider No description ## API Common props ref：[Common props](/docs/react/common-props) ```jsx ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | description | Customize description | ReactNode | - | | | image | Customize image. Will treat as image url when string provided | ReactNode | `Empty.PRESENTED_IMAGE_DEFAULT` | | | imageStyle | The style of image | CSSProperties | - | | ## Built-in images - Empty.PRESENTED_IMAGE_SIMPLE
    - Empty.PRESENTED_IMAGE_DEFAULT
    ## Semantic DOM ## Design Token --- Title: Cascader URL: https://ant.design/components/cascader --- ## When To Use - When you need to select from a set of associated data set. Such as province/city/district, company level, things classification. - When selecting from a large data set, with multi-stage classifications separated for easy selection. - Chooses cascade items in one float layer for better user experience. ## Examples Basic Default value Custom trigger Hover Disabled option Change on select Multiple ShowCheckedStrategy Size Custom render Search Load Options Lazily Custom Field Names Prefix and Suffix Custom dropdown Placement Variants Status Panel _InternalPanelDoNotUseOrYouWillBeFired Component Token ## API Common props ref：[Common props](/docs/react/common-props) ```jsx ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Show clear button | boolean \| { clearIcon?: ReactNode } | true | 5.8.0: Support object type | | ~~autoClearSearchValue~~ | Whether the current search will be cleared on selecting an item. Only applies when `multiple` is `true` | boolean | true | 5.9.0 | | autoFocus | If get focus when component mounted | boolean | false | | | changeOnSelect | Change value on each selection if set to true, see above demo for details | boolean | false | | | className | The additional css class | string | - | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.25.0 | | defaultOpen | Initial visible of cascader popup | boolean | - | | | defaultValue | Initial selected value | string\[] \| number\[] | \[] | | | disabled | Whether disabled select | boolean | false | | | displayRender | The render function of displaying selected options | (label, selectedOptions) => ReactNode | label => label.join(`/`) | `multiple`: 4.18.0 | | tagRender | Custom render function for tags in `multiple` mode | (label: string, onClose: function, value: string) => ReactNode | - | | | ~~popupClassName~~ | The additional className of popup overlay, use `classNames.popup.root` instead | string | - | 4.23.0 | | ~~dropdownRender~~ | Customize dropdown content, use `popupRender` instead | (menus: ReactNode) => ReactNode | - | 4.4.0 | | popupRender | Customize dropdown content | (menus: ReactNode) => ReactNode | - | | | ~~dropdownStyle~~ | The style of dropdown menu, use `styles.popup.root` instead | CSSProperties | - | | | expandIcon | Customize the current item expand icon | ReactNode | - | 4.4.0 | | expandTrigger | expand current item when click or hover, one of `click` `hover` | string | `click` | | | fieldNames | Custom field name for label and value and children | object | { label: `label`, value: `value`, children: `children` } | | | getPopupContainer | Parent Node which the selector should be rendered to. Default to `body`. When position issues happen, try to modify it into scrollable content and position it relative. [example](https://codepen.io/afc163/pen/zEjNOy?editors=0010) | function(triggerNode) | () => document.body | | | loadData | To load option lazily, and it cannot work with `showSearch` | (selectedOptions) => void | - | | | maxTagCount | Max tag count to show. `responsive` will cost render performance | number \| `responsive` | - | 4.17.0 | | maxTagPlaceholder | Placeholder for not showing tags | ReactNode \| function(omittedValues) | - | 4.17.0 | | maxTagTextLength | Max tag text length to show | number | - | 4.17.0 | | notFoundContent | Specify content to show when no result matches | ReactNode | `Not Found` | | | open | Set visible of cascader popup | boolean | - | 4.17.0 | | options | The data options of cascade | [Option](#option)\[] | - | | | placeholder | The input placeholder | string | - | | | placement | Use preset popup align config from builtinPlacements | `bottomLeft` `bottomRight` `topLeft` `topRight` | `bottomLeft` | 4.17.0 | | prefix | The custom prefix | ReactNode | - | 5.22.0 | | showSearch | Whether show search input in single mode | boolean \| [Object](#showsearch) | false | | | size | The input size | `large` \| `middle` \| `small` | - | | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.25.0 | | suffixIcon | The custom suffix icon | ReactNode | - | | | value | The selected value | string\[] \| number\[] | - | | | variant | Variants of selector | `outlined` \| `borderless` \| `filled` \| `underlined` | `outlined` | 5.13.0 \| `underlined`: 5.24.0 | | onChange | Callback when finishing cascader select | (value, selectedOptions) => void | - | | | ~~onDropdownVisibleChange~~ | Callback when popup shown or hidden, use `onOpenChange` instead | (value) => void | - | 4.17.0 | | onOpenChange | Callback when popup shown or hidden | (value) => void | - | | | multiple | Support multiple or not | boolean | - | 4.17.0 | | removeIcon | The custom remove icon | ReactNode | - | | | showCheckedStrategy | The way show selected item in box. ** `SHOW_CHILD`: ** just show child treeNode. **`Cascader.SHOW_PARENT`:** just show parent treeNode (when all child treeNode under the parent treeNode are checked) | `Cascader.SHOW_PARENT` \| `Cascader.SHOW_CHILD` | `Cascader.SHOW_PARENT` | 4.20.0 | | ~~searchValue~~ | Set search value, Need work with `showSearch` | string | - | 4.17.0 | | ~~onSearch~~ | The callback function triggered when input changed | (search: string) => void | - | 4.17.0 | | ~~dropdownMenuColumnStyle~~ | The style of the drop-down menu column, use `popupMenuColumnStyle` instead | CSSProperties | - | | | popupMenuColumnStyle | The style of the drop-down menu column | CSSProperties | - | | | loadingIcon | The appearance of lazy loading (now is useless) | ReactNode | - | | | optionRender | Customize the rendering dropdown options | (option: Option) => React.ReactNode | - | 5.16.0 | ### showSearch | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoClearSearchValue | Whether the current search will be cleared on selecting an item. Only applies when `multiple` is `true` | boolean | true | 5.9.0 | | filter | The function will receive two arguments, inputValue and option, if the function returns true, the option will be included in the filtered set; Otherwise, it will be excluded | function(inputValue, path): boolean | - | | | limit | Set the count of filtered items | number \| false | 50 | | | matchInputWidth | Whether the width of list matches input, ([how it looks](https://github.com/ant-design/ant-design/issues/25779)) | boolean | true | | | render | Used to render filtered options | function(inputValue, path): ReactNode | - | | | sort | Used to sort filtered options | function(a, b, inputValue) | - | | | searchValue | Set search value, Need work with `showSearch` | string | - | 4.17.0 | | onSearch | The callback function triggered when input changed | (search: string) => void | - | 4.17.0 | ### Option ```typescript interface Option { value: string | number; label?: React.ReactNode; disabled?: boolean; children?: Option[]; // Determines if this is a leaf node(effective when `loadData` is specified). // `false` will force trade TreeNode as a parent node. // Show expand icon even if the current node has no children. isLeaf?: boolean; } ``` ## Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ## Semantic DOM ## Design Token --- Title: Card URL: https://ant.design/components/card --- ## When To Use A card can be used to display content related to a single subject. The content can consist of multiple elements of varying types and sizes. ## Examples Basic card No border Simple card Customized content Card in column Loading card Grid card Inner card With tabs Support more content configuration Component Token ## API Common props ref：[Common props](/docs/react/common-props) ```jsx Card content ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | actions | The action list, shows at the bottom of the Card | Array<ReactNode> | - | | | activeTabKey | Current TabPane's key | string | - | | | ~~bordered~~ | Toggles rendering of the border around the card, please use `variant` instead | boolean | true | | | variant | Variants of Card | `outlined` \| `borderless` \| | `outlined` | 5.24.0 | | cover | Card cover | ReactNode | - | | | defaultActiveTabKey | Initial active TabPane's key, if `activeTabKey` is not set | string | `The key of first tab` | | | extra | Content to render in the top-right corner of the card | ReactNode | - | | | hoverable | Lift up when hovering card | boolean | false | | | loading | Shows a loading indicator while the contents of the card are being fetched | boolean | false | | | size | Size of card | `default` \| `small` | `default` | | | tabBarExtraContent | Extra content in tab bar | ReactNode | - | | | tabList | List of TabPane's head | [TabItemType](/components/tabs#tabitemtype)[] | - | | | tabProps | [Tabs](/components/tabs/#tabs) | - | - | | | title | Card title | ReactNode | - | | | type | Card style type, can be set to `inner` or not set | string | - | | | classNames | Config Card build-in module's className | [Record](#semantic-dom) | - | 5.14.0 | | styles | Config Card build-in module's style | [Record](#semantic-dom) | - | 5.14.0 | | onTabChange | Callback when tab is switched | (key) => void | - | | ### Card.Grid | Property | Description | Type | Default | Version | | --------- | ------------------------------- | ------------- | ------- | ------- | | className | The className of container | string | - | | | hoverable | Lift up when hovering card grid | boolean | true | | | style | The style object of container | CSSProperties | - | | ### Card.Meta | Property | Description | Type | Default | Version | | ----------- | ----------------------------- | ------------- | ------- | ------- | | avatar | Avatar or icon | ReactNode | - | | | className | The className of container | string | - | | | description | Description content | ReactNode | - | | | style | The style object of container | CSSProperties | - | | | title | Title content | ReactNode | - | | ## Semantic DOM ### Card ### Card.Meta ## Design Token --- Title: Calendar URL: https://ant.design/components/calendar --- ## When To Use When data is in the form of dates, such as schedules, timetables, prices calendar, lunar calendar. This component also supports Year/Month switch. ## Examples Basic Notice Calendar Card Selectable Calendar Lunar Calendar Show Week Customize Header Component Token ## API Common props ref：[Common props](/docs/react/common-props) **Note:** Part of the Calendar's locale is read from `value`. So, please set the locale of `dayjs` correctly. ```jsx // The default locale is en-US, if you want to use other locale, just set locale in entry file globally. // import dayjs from 'dayjs'; // import 'dayjs/locale/zh-cn'; // dayjs.locale('zh-cn'); ``` | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | cellRender | Customize cell content | function(current: dayjs, info: { prefixCls: string, originNode: React.ReactElement, today: dayjs, range?: 'start' \| 'end', type: PanelMode, locale?: Locale, subType?: 'hour' \| 'minute' \| 'second' \| 'meridiem' }) => React.ReactNode | - | 5.4.0 | | dateFullCellRender | Customize the display of the date cell, the returned content will override the cell | function(date: Dayjs): ReactNode | - | | | fullCellRender | Customize cell content | function(current: dayjs, info: { prefixCls: string, originNode: React.ReactElement, today: dayjs, range?: 'start' \| 'end', type: PanelMode, locale?: Locale, subType?: 'hour' \| 'minute' \| 'second' \| 'meridiem' }) => React.ReactNode | - | 5.4.0 | | defaultValue | The date selected by default | [dayjs](https://day.js.org/) | - | | | disabledDate | Function that specifies the dates that cannot be selected, `currentDate` is same dayjs object as `value` prop which you shouldn't mutate it](https://github.com/ant-design/ant-design/issues/30987) | (currentDate: Dayjs) => boolean | - | | | fullscreen | Whether to display in full-screen | boolean | true | | | showWeek | Whether to display week number | boolean | false | 5.23.0 | | headerRender | Render custom header in panel | function(object:{value: Dayjs, type: 'year' \| 'month', onChange: f(), onTypeChange: f()}) | - | | | locale | The calendar's locale | object | [(default)](https://github.com/ant-design/ant-design/blob/master/components/date-picker/locale/example.json) | | | mode | The display mode of the calendar | `month` \| `year` | `month` | | | validRange | To set valid range | \[[dayjs](https://day.js.org/), [dayjs](https://day.js.org/)] | - | | | value | The current selected date | [dayjs](https://day.js.org/) | - | | | onChange | Callback for when date changes | function(date: Dayjs) | - | | | onPanelChange | Callback for when panel changes | function(date: Dayjs, mode: string) | - | | | onSelect | Callback for when a date is selected, include source info | function(date: Dayjs, info: { source: 'year' \| 'month' \| 'date' \| 'customize' }) | - | `info`: 5.6.0 | ## Semantic DOM ## Design Token ## FAQ ### How to use Calendar with customize date library? See [Use custom date library](/docs/react/use-custom-date-library#calendar) ### How to set locale for date-related components? See [How to set locale for date-related components](/components/date-picker/#localization) ### Date-related components locale is not working? See FAQ [Date-related-components-locale-is-not-working?](/docs/react/faq#date-related-components-locale-is-not-working) ### How to get date from panel click? `onSelect` provide `info.source` to help on this: ```tsx { if (source === 'date') { console.log('Panel Select:', source); } }} /> ``` --- Title: Carousel URL: https://ant.design/components/carousel --- ## When To Use - When there is a group of content on the same level. - When there is insufficient content space, it can be used to save space in the form of a revolving door. - Commonly used for a group of pictures/cards. ## Examples Basic Position Scroll automatically Fade in Arrows for switching Progress of dots Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | arrows | Whether to show switch arrows | boolean | false | 5.17.0 | | autoplay | Whether to scroll automatically, you can specify `autoplay={{ dotDuration: true }}` to display the progress bar | boolean \| { dotDuration?: boolean } | false | dotDuration: 5.24.0 | | autoplaySpeed | Delay between each auto scroll (in milliseconds) | number | 3000 | | | adaptiveHeight | Adjust the slide's height automatically | boolean | false | | | dotPlacement | The position of the dots, which can be one of `top` `bottom` `start` `end` | string | `bottom` | | | ~~dotPosition~~ | The position of the dots, which can be one of `top` `bottom` `left` `right` `start` `end`, Please use `dotPlacement` instead | string | `bottom` | | | dots | Whether to show the dots at the bottom of the gallery, `object` for `dotsClass` | boolean \| { className?: string } | true | | | draggable | Enable scrollable via dragging on desktop | boolean | false | | | fade | Whether to use fade transition | boolean | false | | | infinite | Infinitely wrap around contents | boolean | true | | | speed | Animation speed in milliseconds | number | 500 | | | easing | Transition interpolation function name | string | `linear` | | | effect | Transition effect | `scrollx` \| `fade` | `scrollx` | | | afterChange | Callback function called after the current index changes | (current: number) => void | - | | | beforeChange | Callback function called before the current index changes | (current: number, next: number) => void | - | | | waitForAnimate | Whether to wait for the animation when switching | boolean | false | | Find more APIs in react-slick [documentation](https://react-slick.neostack.com/docs/api). ## Methods | Name | Description | | --- | --- | | goTo(slideNumber, dontAnimate) | Go to slide index, if dontAnimate=true, it happens without animation | | next() | Change current slide to next slide | | prev() | Change current slide to previous slide | ## Design Token ## FAQ ### How to add custom arrows? See [#12479](https://github.com/ant-design/ant-design/issues/12479). --- Title: Checkbox URL: https://ant.design/components/checkbox --- ## When To Use - Used for selecting multiple values from several options. - If you use only one checkbox, it is the same as using Switch to toggle between two states. The difference is that Switch will trigger the state change directly, but Checkbox just marks the state as changed and this needs to be submitted. ## Examples Basic Disabled Controlled Checkbox Checkbox Group Check all Use with Grid Same line Disabled to show Tooltip customize lineWidth ## API Common props ref：[Common props](/docs/react/common-props) #### Checkbox | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoFocus | If get focus when component mounted | boolean | false | | | checked | Specifies whether the checkbox is selected | boolean | false | | | defaultChecked | Specifies the initial state: whether or not the checkbox is selected | boolean | false | | | disabled | If disable checkbox | boolean | false | | | indeterminate | The indeterminate checked state of checkbox | boolean | false | | | onChange | The callback function that is triggered when the state changes | (e: CheckboxChangeEvent) => void | - | | | onBlur | Called when leaving the component | function() | - | | | onFocus | Called when entering the component | function() | - | | #### Checkbox.Group | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | defaultValue | Default selected value | (string \| number)\[] | \[] | | | disabled | If disable all checkboxes | boolean | false | | | name | The `name` property of all `input[type="checkbox"]` children | string | - | | | options | Specifies options | string\[] \| number\[] \| Option\[] | \[] | | | value | Used for setting the currently selected value | (string \| number \| boolean)\[] | \[] | | | title | title of the option | `string` | - | | | className | className of the option | `string` | - | 5.25.0 | | style | styles of the option | `React.CSSProperties` | - | | | onChange | The callback function that is triggered when the state changes | (checkedValue: T[]) => void | - | | ##### Option ```typescript interface Option { label: string; value: string; disabled?: boolean; } ``` ### Methods #### Checkbox | Name | Description | Version | | ------------- | ------------------------------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | | nativeElement | Returns the DOM node of the Checkbox | 5.17.3 | ## Semantic DOM ## Design Token ## FAQ ### Why not work in Form.Item? Form.Item default bind value to `value` property, but Checkbox value property is `checked`. You can use `valuePropName` to change bind property. ```tsx | pure ``` --- Title: Avatar URL: https://ant.design/components/avatar --- ## Examples Basic Type Autoset Font Size With Badge Avatar.Group Calculate text style when hiding Responsive Size Fallback Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Avatar | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | alt | This attribute defines the alternative text describing the image | string | - | | | gap | Letter type unit distance between left and right sides | number | 4 | 4.3.0 | | icon | Custom icon type for an icon avatar | ReactNode | - | | | shape | The shape of avatar | `circle` \| `square` | `circle` | | | size | The size of the avatar | number \| `large` \| `small` \| `default` \| { xs: number, sm: number, ...} | `default` | 4.7.0 | | src | The address of the image for an image avatar or image element | string \| ReactNode | - | ReactNode: 4.8.0 | | srcSet | A list of sources to use for different screen resolutions | string | - | | | draggable | Whether the picture is allowed to be dragged | boolean \| `'true'` \| `'false'` | true | | | crossOrigin | CORS settings attributes | `'anonymous'` \| `'use-credentials'` \| `''` | - | 4.17.0 | | onError | Handler when img load error, return false to prevent default fallback behavior | () => boolean | - | | > Tip: You can set `icon` or `children` as the fallback for image load error, with the priority of `icon` > `children` ### Avatar.Group 4.5.0+ | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | max | Set maximum display related configurations, Before `5.18.0` you can use [parameters](https://github.com/ant-design/ant-design/blob/9d134859becbdae5b9ce276f6d9af4264691d81f/components/avatar/group.tsx#L35-L38) | `{ count?: number; style?: CSSProperties; popover?: PopoverProps }` | - | 5.18.0 | | size | The size of the avatar | number \| `large` \| `small` \| `default` \| { xs: number, sm: number, ...} | `default` | 4.8.0 | | shape | The shape of the avatar | `circle` \| `square` | `circle` | 5.8.0 | ## Design Token --- Title: Button URL: https://ant.design/components/button --- ## When To Use A button means an operation (or a series of operations). Clicking a button will trigger its corresponding business logic. In Ant Design we provide 5 types of button. - 🔵 Primary button: used for the main action, there can be at most one primary button in a section. - ⚪️ Default button: used for a series of actions without priority. - 😶 Dashed button: commonly used for adding more actions. - 🔤 Text button: used for the most secondary action. - 🔗 Link button: used for external links. And 4 other properties additionally. - 🔴 `danger`: used for actions of risk, like deletion or authorization. - 👻 `ghost`: used in situations with complex background, home pages usually. - 🚫 `disabled`: used when actions are not available. - 🔃 `loading`: adds a loading spinner in button, avoids multiple submits too. ## Examples Syntactic sugar Color & Variant Debug Color & Variant Icon Icon Placement Debug Icon Debug Block Size Disabled Loading Multiple Buttons Ghost Button Danger Buttons Block Button Deprecated Button Group Loading style bug Component Token Gradient Button Custom disabled backgroundColor ## API Common props ref：[Common props](/docs/react/common-props) Different button styles generated by setting Button properties. The recommended order is: `type` -> `shape` -> `size` -> `loading` -> `disabled`. | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | autoInsertSpace | We add a space between two Chinese characters by default, which removed by setting `autoInsertSpace` to `false`. | boolean | `true` | 5.17.0 | | block | Option to fit button width to its parent width | boolean | false | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.4.0 | | color | Set button color | `default` \| `primary` \| `danger` \| [PresetColors](#presetcolors) | - | `default`, `primary` and `danger`: 5.21.0, `PresetColors`: 5.23.0 | | danger | Syntactic sugar. Set the danger status of button. will follow `color` if provided | boolean | false | | | disabled | Disabled state of button | boolean | false | | | ghost | Make background transparent and invert text and border colors | boolean | false | | | href | Redirect url of link button | string | - | | | htmlType | Set the original html `type` of `button`, see: [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button#type) | `submit` \| `reset` \| `button` | `button` | | | icon | Set the icon component of button | ReactNode | - | | | ~~iconPosition~~ | Set the icon position of button, please use `iconPlacement` instead | `start` \| `end` | `start` | 5.17.0 | | iconPlacement | Set the icon position of button | `start` \| `end` | `start` | - | | loading | Set the loading status of button | boolean \| { delay: number, icon: ReactNode } | false | icon: 5.23.0 | | shape | Can be used to set button shape | `default` \| `circle` \| `round` | `default` | | | size | Set the size of button | `large` \| `middle` \| `small` | `middle` | | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.4.0 | | target | Same as target attribute of a, works when href is specified | string | - | | | type | Syntactic sugar. Set button type. Will follow `variant` & `color` if provided | `primary` \| `dashed` \| `link` \| `text` \| `default` | `default` | | | onClick | Set the handler to handle `click` event | (event: React.MouseEvent) => void | - | | | variant | Set button variant | `outlined` \| `dashed` \| `solid` \| `filled` \| `text` \| `link` | - | 5.21.0 | It accepts all props which native buttons support. ### PresetColors > type PresetColors = 'blue' | 'purple' | 'cyan' | 'green' | 'magenta' | 'pink' | 'red' | 'orange' | 'yellow' | 'volcano' | 'geekblue' | 'lime' | 'gold'; ## Semantic DOM ## Design Token ## FAQ ### How to choose type and color & variant? {#faq-type-color-variant} Type is essentially syntactic sugar for colors and variants. It internally provides a set of mapping relationships between colors and variants for the type. If both exist at the same time, the colors and variants will be used first. ```jsx ``` Equivalent ```jsx ``` ### How to close the click wave effect? {#faq-close-wave-effect} If you don't need this feature, you can set `disabled` of `wave` in [ConfigProvider](/components/config-provider#api) as `true`. ```jsx ``` --- Title: Badge URL: https://ant.design/components/badge --- ## When To Use Badge normally appears in proximity to notifications or user avatars with eye-catching appeal, typically displaying unread messages count. ## Examples Basic Standalone Overflow Count Red badge Dynamic Clickable Offset Size Status Colorful Badge Ribbon Ribbon Debug Mixed usage Title Colorful Badge support count Debug Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Badge | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | color | Customize Badge dot color | string | - | | | count | Number to show in badge | ReactNode | - | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.7.0 | | dot | Whether to display a red dot instead of `count` | boolean | false | | | offset | Set offset of the badge dot | \[number, number] | - | | | overflowCount | Max count to show | number | 99 | | | showZero | Whether to show badge when `count` is zero | boolean | false | | | size | If `count` is set, `size` sets the size of badge | `default` \| `small` | - | - | | status | Set Badge as a status dot | `success` \| `processing` \| `default` \| `error` \| `warning` | - | | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.7.0 | | text | If `status` is set, `text` sets the display text of the status `dot` | ReactNode | - | | | title | Text to show when hovering over the badge | string | - | | ### Badge.Ribbon | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | color | Customize Ribbon color | string | - | | | placement | The placement of the Ribbon, `start` and `end` follow text direction (RTL or LTR) | `start` \| `end` | `end` | | | text | Content inside the Ribbon | ReactNode | - | | ## Semantic DOM ### Badge ### Badge.Ribbon ## Design Token --- Title: Anchor URL: https://ant.design/components/anchor --- ## When To Use For displaying anchor hyperlinks on page and jumping between them. > Notes for developers > > After version `4.24.0`, we rewrite Anchor use FC, Some methods of obtaining `ref` and calling internal instance methods will invalid. ## Examples Basic Horizontal Anchor Static Anchor Customize the onClick event Customize the anchor highlight Set Anchor scroll offset Listening for anchor link change Replace href in history Deprecated JSX demo Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Anchor Props | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | affix | Fixed mode of Anchor | boolean \| Omit | true | object: 5.19.0 | | bounds | Bounding distance of anchor area | number | 5 | | | getContainer | Scrolling container | () => HTMLElement | () => window | | | getCurrentAnchor | Customize the anchor highlight | (activeLink: string) => string | - | | | offsetTop | Pixels to offset from top when calculating position of scroll | number | 0 | | | showInkInFixed | Whether show ink-square when `affix={false}` | boolean | false | | | targetOffset | Anchor scroll offset, default as `offsetTop`, [example](#anchor-demo-targetoffset) | number | - | | | onChange | Listening for anchor link change | (currentActiveLink: string) => void | | | | onClick | Set the handler to handle `click` event | (e: MouseEvent, link: object) => void | - | | | items | Data configuration option content, support nesting through children | { key, href, title, target, children }\[] [see](#anchoritem) | - | 5.1.0 | | direction | Set Anchor direction | `vertical` \| `horizontal` | `vertical` | 5.2.0 | | replace | Replace items' href in browser history instead of pushing it | boolean | false | 5.7.0 | ### AnchorItem | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | key | The unique identifier of the Anchor Link | string \| number | - | | | href | The target of hyperlink | string | | | | target | Specifies where to display the linked URL | string | | | | title | The content of hyperlink | ReactNode | | | | children | Nested Anchor Link, `Attention: This attribute does not support horizontal orientation` | [AnchorItem](#anchoritem)\[] | - | | | replace | Replace item href in browser history instead of pushing it | boolean | false | 5.7.0 | ### Link Props We recommend using the items form instead. | Property | Description | Type | Default | Version | | -------- | ----------------------------------------- | --------- | ------- | ------- | | href | The target of hyperlink | string | | | | target | Specifies where to display the linked URL | string | | | | title | The content of hyperlink | ReactNode | | | ## Semantic DOM ## Design Token ## FAQ ### In version `5.25.0+`, the `:target` pseudo-class of the destination element does not take effect as expected after anchor navigation. For the purpose of page performance optimization, the implementation of anchor navigation has been changed from `window.location.href` to `window.history.pushState/replaceState`. Since `pushState/replaceState` does not trigger a page reload, the browser will not automatically update the matching state of the `:target` pseudo-class. To resolve this issue, you can manually construct the full URL: `href = window.location.origin + window.location.pathname + '#xxx'`. Related issues: [#53143](https://github.com/ant-design/ant-design/issues/53143) [#54255](https://github.com/ant-design/ant-design/issues/54255) --- Title: Breadcrumb URL: https://ant.design/components/breadcrumb --- ## When To Use - When the system has more than two layers in a hierarchy. - When you need to inform the user of where they are. - When the user may need to navigate back to a higher level. ```jsx // works when >=5.3.0, recommended ✅ return ; // works when <5.3.0, deprecated when >=5.3.0 🙅🏻‍♀️ return ( sample ); // or return ; ``` ## Examples Basic Usage With an Icon With Params Configuring the Separator Bread crumbs with drop down menu Configuring the Separator Independently Debug Routes Component Token ## API Common props ref：[Common props](/docs/react/common-props) ### Breadcrumb | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | itemRender | Custom item renderer | (route, params, routes, paths) => ReactNode | - | | | params | Routing parameters | object | - | | | items | The routing stack information of router | [ItemType\[\]](#itemtype) | - | 5.3.0 | | separator | Custom separator | ReactNode | `/` | | ### ItemType > type ItemType = Omit<[RouteItemType](#routeitemtype), 'title' | 'path'> | [SeparatorType](#separatortype) ### RouteItemType | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | className | The additional css class | string | - | | | dropdownProps | The dropdown props | [Dropdown](/components/dropdown) | - | | | href | Target of hyperlink. Can not work with `path` | string | - | | | path | Connected path. Each path will connect with prev one. Can not work with `href` | string | - | | | menu | The menu props | [MenuProps](/components/menu/#api) | - | 4.24.0 | | onClick | Set the handler to handle click event | (e:MouseEvent) => void | - | | | title | item name | ReactNode | - | | ### SeparatorType ```ts const item = { type: 'separator', // Must have separator: '/', }; ``` | Property | Description | Type | Default | Version | | --------- | ----------------- | ----------- | ------- | ------- | | type | Mark as separator | `separator` | | 5.3.0 | | separator | Custom separator | ReactNode | `/` | 5.3.0 | ### Use with browserHistory The link of Breadcrumb item targets `#` by default, you can use `itemRender` to make a `browserHistory` Link. ```jsx import { Link } from 'react-router'; const items = [ { path: '/index', title: 'home', }, { path: '/first', title: 'first', children: [ { path: '/general', title: 'General', }, { path: '/layout', title: 'Layout', }, { path: '/navigation', title: 'Navigation', }, ], }, { path: '/second', title: 'second', }, ]; function itemRender(currentRoute, params, items, paths) { const isLast = currentRoute?.path === items[items.length - 1]?.path; return isLast ? ( {currentRoute.title} ) : ( {currentRoute.title} ); } return ; ``` ## Semantic DOM ## Design Token --- Title: Affix URL: https://ant.design/components/affix --- ## When To Use On longer web pages, it's helpful to stick component into the viewport. This is common for menus and actions. Please note that Affix should not cover other content on the page, especially when the size of the viewport is small. > Notes for developers > > After version `5.10.0`, we rewrite Affix use FC, Some methods of obtaining `ref` and calling internal instance methods will invalid. ## Examples Basic Callback Container to scroll. debug ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | | --- | --- | --- | --- | | offsetBottom | Offset from the bottom of the viewport (in pixels) | number | - | | offsetTop | Offset from the top of the viewport (in pixels) | number | 0 | | target | Specifies the scrollable area DOM node | () => HTMLElement | () => window | | onChange | Callback for when Affix state is changed | (affixed?: boolean) => void | - | **Note:** Children of `Affix` must not have the property `position: absolute`, but you can set `position: absolute` on `Affix` itself: ```jsx ... ``` ## FAQ ### When binding container with `target` in Affix, elements sometimes move out of the container. We only listen to container scroll events for performance consideration. You can add custom listeners if you still want to: Related issues：[#3938](https://github.com/ant-design/ant-design/issues/3938) [#5642](https://github.com/ant-design/ant-design/issues/5642) [#16120](https://github.com/ant-design/ant-design/issues/16120) ### When Affix is ​​used in a horizontal scroll container, the position of the element `left` is incorrect. Affix is ​​generally only applicable to areas with one-way scrolling, and only supports usage in vertical scrolling containers. If you want to use it in a horizontal container, you can consider implementing with the native `position: sticky` property. Related issues：[#29108](https://github.com/ant-design/ant-design/issues/29108) --- Title: Util URL: https://ant.design/components/_util --- Available since `5.13.0`. ## GetRef Get the `ref` property definition of the component, which is very useful for components that are not directly exposed or child components. ```tsx import { Select } from 'antd'; import type { GetRef } from 'antd'; type SelectRefType = GetRef; // BaseSelectRef ``` ## GetProps Get the `props` property definition of the component: ```tsx import { Checkbox } from 'antd'; import type { GetProps } from 'antd'; type CheckboxGroupType = GetProps; ``` Also supports getting the property definition of Context: ```tsx import type { GetProps } from 'antd'; interface InternalContextProps { name: string; } const Context = React.createContext({ name: 'Ant Design' }); type ContextType = GetProps; // InternalContextProps ``` ## GetProp Get the single `props` or `context` property definition of the component. It has encapsulated `NonNullable`, so you don't have to worry about it being empty: ```tsx import { Select } from 'antd'; import type { GetProp, SelectProps } from 'antd'; // Both of these can work type SelectOptionType1 = GetProp[number]; type SelectOptionType2 = GetProp[number]; type ContextOptionType = GetProp; ``` --- Title: AutoComplete URL: https://ant.design/components/auto-complete --- ## When To Use - When you need an input box instead of a selector. - When you need input suggestions or helping text. The differences with Select are: - AutoComplete is an input box with text hints, and users can type freely. The keyword is aiding **input**. - Select is selecting among given choices. The keyword is **select**. ## Examples Basic Usage Customized Customize Input Component Non-case-sensitive AutoComplete Lookup-Patterns - Certain Category Lookup-Patterns - Uncertain Category Status Variants Customize clear button Debug in Form AutoComplete and Select _InternalPanelDoNotUseOrYouWillBeFired ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | allowClear | Show clear button | boolean \| { clearIcon?: ReactNode } | false | 5.8.0: Support Object type | | autoFocus | If get focus when component mounted | boolean | false | | | backfill | If backfill selected item the input when using keyboard | boolean | false | | | children (for customize input element) | Customize input element | HTMLInputElement \| HTMLTextAreaElement \| React.ReactElement<InputProps> | <Input /> | | | children (for dataSource) | Data source to auto complete | React.ReactElement<OptionProps> \| Array<React.ReactElement<OptionProps>> | - | | | classNames | Semantic DOM class | [Record](#semantic-dom) | - | 5.25.0 | | defaultActiveFirstOption | Whether active first option by default | boolean | true | | | defaultOpen | Initial open state of dropdown | boolean | - | | | defaultValue | Initial selected option | string | - | | | disabled | Whether disabled select | boolean | false | | | ~~dropdownRender~~ | Customize dropdown content, use `popupRender` instead | (originNode: ReactNode) => ReactNode | - | 4.24.0 | | popupRender | Customize dropdown content | (originNode: ReactNode) => ReactNode | - | | | ~~dropdownStyle~~ | The style of dropdown menu, use `styles.popup.root` instead | CSSProperties | - | | | ~~popupClassName~~ | The className of dropdown menu, use `classNames.popup.root` instead | string | - | 4.23.0 | | popupMatchSelectWidth | Determine whether the dropdown menu and the select input are the same width. Default set `min-width` same as input. Will ignore when value less than select width. `false` will disable virtual scroll | boolean \| number | true | | | ~~filterOption~~ | If true, filter options by input, if function, filter options against it. The function will receive two arguments, `inputValue` and `option`, if the function returns true, the option will be included in the filtered set; Otherwise, it will be excluded | boolean \| function(inputValue, option) | true | | | getPopupContainer | Parent node of the dropdown. Default to body, if you encountered positioning problems during scroll, try changing to the scrollable area and position relative to it. [Example](https://codesandbox.io/s/4j168r7jw0) | function(triggerNode) | () => document.body | | | notFoundContent | Specify content to show when no result matches | ReactNode | - | | | open | Controlled open state of dropdown | boolean | - | | | options | Select options. Will get better perf than jsx definition | { label, value }\[] | - | | | placeholder | The placeholder of input | string | - | | | showSearch | search for configuration | true \| [Object](#showsearch) | true | | | status | Set validation status | 'error' \| 'warning' | - | 4.19.0 | | size | The size of the input box | `large` \| `middle` \| `small` | - | | | value | Selected option | string | - | | | styles | Semantic DOM style | [Record](#semantic-dom) | - | 5.25.0 | | variant | Variants of input | `outlined` \| `borderless` \| `filled` | `outlined` | 5.13.0 | | virtual | Disable virtual scroll when set to false | boolean | true | 4.1.0 | | onBlur | Called when leaving the component | function() | - | | | onChange | Called when selecting an option or changing an input value | function(value) | - | | | ~~onDropdownVisibleChange~~ | Called when dropdown open, use `onOpenChange` instead | (open: boolean) => void | - | | | onOpenChange | Called when dropdown open | (open: boolean) => void | - | | | onFocus | Called when entering the component | function() | - | | | ~~onSearch~~ | Called when searching items | function(value) | - | | | onSelect | Called when a option is selected. param is option's value and option instance | function(value, option) | - | | | onClear | Called when clear | function | - | 4.6.0 | | onInputKeyDown | Called when key pressed | (event: KeyboardEvent) => void | - | | | onPopupScroll | Called when dropdown scrolls | (event: UIEvent) => void | - | | ### showSearch | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | filterOption | If true, filter options by input, if function, filter options against it. The function will receive two arguments, `inputValue` and `option`, if the function returns true, the option will be included in the filtered set; Otherwise, it will be excluded | boolean \| function(inputValue, option) | true | | | onSearch | Called when searching items | function(value) | - | | ## Methods | Name | Description | Version | | ------- | ------------ | ------- | | blur() | Remove focus | | | focus() | Get focus | | ## Semantic DOM ## Design Token ## FAQ ### Why doesn't the text composition system work well with onSearch in controlled mode? Please use `onChange` to manage control state. `onSearch` is used for searching input which is not the same as `onChange`. Besides, clicking on the option will not trigger the `onSearch` event. Related issue: [#18230](https://github.com/ant-design/ant-design/issues/18230) [#17916](https://github.com/ant-design/ant-design/issues/17916) ### Why won't a controlled open AutoComplete display a drop-down menu when options are empty? The AutoComplete component is essentially an extension of the Input form element. When the `options` property is empty, displaying empty text could mislead the user into believing the component is not operational, when in fact they are still able to input text. To avoid confusion, the `open` property will not display the drop-down menu when set to `true` and in combination with an empty `options` property. The `open` property must be used in conjunction with the `options` property. --- Title: Alert URL: https://ant.design/components/alert --- ## When To Use - When you need to show alert messages to users. - When you need a persistent static container which is closable by user actions. ## Examples Basic More types Closable Description Icon Banner Loop Banner Smoothly Unmount ErrorBoundary Custom Icon Custom action Component Token ## API Common props ref：[Common props](/docs/react/common-props) | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | action | The action of Alert | ReactNode | - | 4.9.0 | | afterClose | Called when close animation is finished | () => void | - | | | banner | Whether to show as banner | boolean | false | | | closable | The config of closable, >=5.15.0: support `aria-*` | boolean \| ({ closeIcon?: React.ReactNode } & React.AriaAttributes) | `false` | | | description | Additional content of Alert | ReactNode | - | | | icon | Custom icon, effective when `showIcon` is true | ReactNode | - | | | ~~message~~ | Content of Alert, please use `title` instead | ReactNode | - | | | title | Content of Alert | ReactNode | - | | | showIcon | Whether to show icon | boolean | false, in `banner` mode default is true | | | type | Type of Alert styles, options: `success`, `info`, `warning`, `error` | string | `info`, in `banner` mode default is `warning` | | | onClose | Callback when Alert is closed | (e: MouseEvent) => void | - | | ### Alert.ErrorBoundary | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | description | Custom error description to show | ReactNode | {{ error stack }} | | | ~~message~~ | Custom error message to show, please use `title` instead | ReactNode | {{ error }} | | | title | Custom error title to show | ReactNode | {{ error }} | | ## Semantic DOM ## Design Token --- Title: App URL: https://ant.design/components/app --- ## When To Use - Provide reset styles based on `.ant-app` element. - You could use static methods of `message/notification/Modal` from `useApp` without writing `contextHolder` manually. ## Examples Basic Hooks config ## How to use ### Basic usage App provides upstream and downstream method calls through `Context`, because useApp needs to be used as a subcomponent, we recommend encapsulating App at the top level in the application. ```tsx import React from 'react'; import { App } from 'antd'; const MyPage: React.FC = () => { const { message, notification, modal } = App.useApp(); message.success('Good!'); notification.info({ title: 'Good' }); modal.warning({ title: 'Good' }); // .... // other message, notification, modal static function return
    Hello word
    ; }; const MyApp: React.FC = () => ( ); export default MyApp; ``` Note: App.useApp must be available under App. ### Sequence with ConfigProvider The App component can only use the token in the `ConfigProvider`, if you need to use the Token, the ConfigProvider and the App component must appear in pairs. ```tsx ... ``` ### Embedded usage scenarios (if not necessary, try not to do nesting) ```tsx ... ... ``` ### Global scene (redux scene) ```tsx // Entry component import { App } from 'antd'; import type { MessageInstance } from 'antd/es/message/interface'; import type { ModalStaticFunctions } from 'antd/es/modal/confirm'; import type { NotificationInstance } from 'antd/es/notification/interface'; let message: MessageInstance; let notification: NotificationInstance; let modal: Omit; export default () => { const staticFunction = App.useApp(); message = staticFunction.message; modal = staticFunction.modal; notification = staticFunction.notification; return null; }; export { message, modal, notification }; ``` ```tsx // sub page import React from 'react'; import { Button, Space } from 'antd'; import { message } from './store'; export default () => { const showMessage = () => { message.success('Success!'); }; return ( ); }; ``` ## API Common props ref：[Common props](/docs/react/common-props) > This component is available since `antd@5.1.0`. ### App | Property | Description | Type | Default | Version | | --- | --- | --- | --- | --- | | component | Config render element, if `false` will not create DOM node | ComponentType \| false | div | 5.11.0 | | message | Global config for Message | [MessageConfig](/components/message/#messageconfig) | - | 5.3.0 | | notification | Global config for Notification | [NotificationConfig](/components/notification/#notificationconfig) | - | 5.3.0 | ## Design Token ## FAQ ### CSS Var doesn't work inside `` Make sure the App `component` is a valid html tag, so when you're turning on CSS variables, there's a container to hold the CSS class name. If not set, it defaults to the `div` tag. If set to `false`, no additional DOM nodes will be created, and no default styles will be provided.