API Naming Convention API 命名统一 #16291
kooriookami
started this conversation in
RFC
Replies: 3 comments
-
add my optionion about css-var RFC: #16709 |
Beta Was this translation helpful? Give feedback.
0 replies
-
tag 有3个api有点奇怪
It's a little weird that tag 3 apis
|
Beta Was this translation helpful? Give feedback.
0 replies
-
我注意到一个有趣的问题, table v2中对于事件放弃了emits的写法,转而使用props(naive-ui也是这么处理的),我猜测这是因为defineEmits的一些局限性, 但是在最新的组件中却还是在使用emits, 我想问一下,开发团队是否会在未来都替换为使用props? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
API Naming Convention API 命名统一
API naming should follow the principle of simplicity and clarity. A list for the naming inconsistencies in the components is open for discussion.
API 命名应该遵循简洁明了的原则。针对组件中命名不统一的地方进行列举,欢迎大家讨论。
Examples 举例
Component Attributes 组件属性
The same functionality across different components should be consistent.
不同的组件相同的功能应该保持一致。
packages/hooks/use-delayed-toggle
延迟显示,请使用
packages/hooks/use-delayed-toggle
packages/hooks/use-delayed-toggle
延迟关闭,请使用
packages/hooks/use-delayed-toggle
Naive Attributes 原生属性
Naive attributes of tags names should be consistent.
标签原生属性名称应该保持一致。
aria-label
attribute原生
aria-label
属性5 votes ·
Beta Was this translation helpful? Give feedback.
All reactions