|
72 | 72 | //! |
73 | 73 | //! # Data Providers |
74 | 74 | //! |
75 | | -//! As shown in the inital usage example, when you add `#[table(impl_vec_data_provider)]` to your struct, |
| 75 | +//! As shown in the initial usage example, when you add `#[table(impl_vec_data_provider)]` to your struct, |
76 | 76 | //! the table will automatically generate a data provider for you. You can then directly pass a `Vec<T>` to the `rows` prop. |
77 | 77 | //! Internally this implements the trait [`TableDataProvider`] for `Vec<T>`. |
78 | 78 | //! |
|
113 | 113 | //! |
114 | 114 | //! These attributes can be applied to any field in the struct. |
115 | 115 | //! |
116 | | -//! - **`class`** - Specifies the classes that are applied to each cell (head and body) in the field's column. Can be used in conjuction with `classes_provider` to customize the classes. |
117 | | -//! - **`head_class`** - Specifies the classes that are applied to the header cell in the field's column. Can be used in conjuction with `classes_provider` to customize the classes. |
118 | | -//! - **`cell_class`** - Specifies the classes that are applied to the body cells in the field's column. Can be used in conjuction with `classes_provider` to customize the classes. |
| 116 | +//! - **`class`** - Specifies the classes that are applied to each cell (head and body) in the field's column. Can be used in conjunction with `classes_provider` to customize the classes. |
| 117 | +//! - **`head_class`** - Specifies the classes that are applied to the header cell in the field's column. Can be used in conjunction with `classes_provider` to customize the classes. |
| 118 | +//! - **`cell_class`** - Specifies the classes that are applied to the body cells in the field's column. Can be used in conjunction with `classes_provider` to customize the classes. |
119 | 119 | //! - **`skip`** - Specifies that the field should be skipped. This is useful for fields that are not displayed in the table. |
120 | 120 | //! - **`skip_sort`** - Only applies if `sortable` is set on the struct. Specifies that the field should not be used for sorting. Clicking it's header will not do anything. |
121 | 121 | //! - **`skip_header`** - Makes the title of the field not be displayed in the head row. |
@@ -172,7 +172,7 @@ pub struct TemperatureMeasurement { |
172 | 172 | //! # Classes Customization |
173 | 173 | //! |
174 | 174 | //! Classes can be easily customized by using the `classes_provider` attribute on the struct. |
175 | | -//! You can specify any type that implementats the trait [`TableClassesProvider`]. Please see the documentation for that trait for more information. |
| 175 | +//! You can specify any type that implements the trait [`TableClassesProvider`]. Please see the documentation for that trait for more information. |
176 | 176 | //! You can also look at [`TailwindClassesPreset`] for an example how this can be implemented. |
177 | 177 | //! |
178 | 178 | //! Example: |
@@ -245,7 +245,7 @@ pub struct TemperatureMeasurement { |
245 | 245 | //! ## When to use `FieldGetter` vs `getter` attribute |
246 | 246 | //! |
247 | 247 | //! A field of type `FieldGetter<T>` is a virtual field that doesn't really exist on the struct. |
248 | | -//! Internally `FieldGetter` is just a new-typed `PhatomData` and thus is removed during compilation. |
| 248 | +//! Internally `FieldGetter` is just a new-typed `PhantomData` and thus is removed during compilation. |
249 | 249 | //! Hence it doesn't increase memory usage. That means you should use it for purely derived data. |
250 | 250 | //! |
251 | 251 | //! The `getter` attribute should be used on a field that actually exists on the struct but whose |
|
0 commit comments