-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core] Clean error messages prefix #2676
Conversation
Do you plan to also update the documentation? |
In the issue description, I didn't try to provide a comprehensive list of the type of references that needs to be updated. I would encourage to do a global search for |
I can update this pr with the other cases yes |
@@ -132,7 +132,7 @@ You can use the [slots API](/components/data-grid/components/#overriding-compone | |||
|
|||
| Name | Type | Default | Description | | |||
|:-----|:-----|:--------|:------------| | |||
| <span class="prop-name">Checkbox</span> | <span class="prop-type">elementType</span> | <span class="prop-type">Checkbox</span> | Checkbox component used in the grid for both header and cells. By default, it uses the Material-UI core Checkbox component. | | |||
| <span class="prop-name">Checkbox</span> | <span class="prop-type">elementType</span> | <span class="prop-type">Checkbox</span> | Checkbox component used in the grid for both header and cells. By default, it uses the MUI core Checkbox component. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <span class="prop-name">Checkbox</span> | <span class="prop-type">elementType</span> | <span class="prop-type">Checkbox</span> | Checkbox component used in the grid for both header and cells. By default, it uses the MUI core Checkbox component. | | |
| <span class="prop-name">Checkbox</span> | <span class="prop-type">elementType</span> | <span class="prop-type">Checkbox</span> | Checkbox component used in the grid for both header and cells. By default, it uses the MUI Core Checkbox component. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between the two lines here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was the same, oops, updated. I wondered about the capitalization of the MUI Core.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we approved this one, could we update the whole codebase? I assume that the source of truth for this one is in the TypeScript' descriptions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we approved this one, could we update the whole codebase? I assume that the source of truth for this one is in the TypeScript' descriptions.
I think it's not worth to waste time updating the manually authored API pages now. The documentation for this component can be automatically generated in #2465. BTW, the TypeScript definition doesn't have the "By default, it uses the MUI..." part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, the TypeScript definition doesn't have the "By default, it uses the MUI..." part.
Oh nice, +1 for ignoring the api .md files and focusing on the TypeScript definition. It started to diverge on this instance with #1528.
Co-authored-by: Olivier Tassinari <[email protected]>
Co-authored-by: Olivier Tassinari <[email protected]>
Co-authored-by: Olivier Tassinari <[email protected]>
Co-authored-by: Olivier Tassinari <[email protected]>
Co-authored-by: Olivier Tassinari <[email protected]>
Co-authored-by: Olivier Tassinari <[email protected]>
packages/grid/_modules_/grid/hooks/features/keyboard/useGridKeyboardNavigation.ts
Outdated
Show resolved
Hide resolved
packages/grid/_modules_/grid/hooks/features/keyboard/useGridKeyboardNavigation.ts
Outdated
Show resolved
Hide resolved
…yboardNavigation.ts Co-authored-by: Matheus Wichman <[email protected]>
Co-authored-by: Matheus Wichman <[email protected]>
…yboardNavigation.ts Co-authored-by: Matheus Wichman <[email protected]>
Co-authored-by: Matheus Wichman <[email protected]>
Co-authored-by: Matheus Wichman <[email protected]>
@@ -1,6 +1,6 @@ | |||
MIT License | |||
|
|||
Copyright (c) 2020 Material-UI SAS | |||
Copyright (c) 2021 Material-UI SAS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, this change is not correct, see https://opensource.stackexchange.com/questions/6389/how-do-the-years-specified-in-a-copyright-statement-work for why. It's meant to signal the first year when the content was created.
@mbrookes A preference on what we should do? Like React or
Copyright (c) 2021 Material-UI SAS | |
Copyright (c) Material-UI SAS |
or as before, the first year
Copyright (c) 2021 Material-UI SAS | |
Copyright (c) 2020 Material-UI SAS |
or a range
Copyright (c) 2021 Material-UI SAS | |
Copyright (c) 2020-2021 Material-UI SAS |
?
I would be leaning to revert, match what we do in the core.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, missed this. Consistent with the core makes sense.
One problem with the year of creation is that it doesn't strictly apply to source code that is changed over the years, unlike say a book which is published in a particular year, and doesn't change. That said, it doesn't much matter, as copyright is implicit, and by the time the copyright expires on the first commits, we'll be beyond caring. Not to mention, for open source, copyright doesn't hold much meaning.
import * as React from 'react'; | ||
|
||
export default function Playground() { | ||
return <div>This file is listed in `.gitignore`</div>; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would have been better as a tsx file, done in #2755.
Closes #2631