Unknown component property | Accept with warning
大多数人认为设计系统应该严格限制和验证所有属性，以确保一致性和可预测性。但作者认为应该接受未知组件属性，但仅发出警告。这种方法挑战了传统设计系统必须严格控制所有方面的观念，提供了一种更为灵活的方法，允许创新和扩展，同时仍保持基本的结构和约束。
7 Matching Annotations
- Last 7 days
-
github.com github.com
-
- Aug 2024
-
-
upport cross-divisional thinking and that the best ideas are already in a company and it's just a matter of sort of um getting people together
for - neuroscience - validation for Stop Reset Go open source participatory system mapping for design innovation
neuroscience - validation for Stop Reset Go open source participatory system mapping for design innovation - bottom-up collective design efficacy - What Henning Beck validates for companies can also apply to using Stop Reset Go participatory system mapping within an open space to de-silo and be as inclusive as possible of many different silo'd transition actors
-
- Mar 2021
-
css-tricks.com css-tricks.com
-
Positively indicate valid input values Let users know a field has been entered correctly. The browser can give us this information through the :valid CSS selector:
-
- Sep 2020
- Dec 2019
-
stackoverflow.com stackoverflow.com
-
Arguably, the rails-team's choice of raising ArgumentError instead of validation error is correct in the sense that we have full control over what options a user can select from a radio buttons group, or can select over a select field, so if a programmer happens to add a new radio button that has a typo for its value, then it is good to raise an error as it is an application error, and not a user error. However, for APIs, this will not work because we do not have any control anymore on what values get sent to the server.
-
-
stackoverflow.com stackoverflow.com
-
When the controller creates the user, instead of adding a validation error to the record, it raises an exception. How to avoid this?
-
In case anyone wants a hack, here is what I came up with.
-