Skip to content

Commit 2df1b4d

Browse files
authored
chore: vale lint issues (#2623)
1 parent 8812be4 commit 2df1b4d

File tree

3 files changed

+20
-18
lines changed

3 files changed

+20
-18
lines changed

.styles/Vocab/Base/accept.txt

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,4 +40,6 @@ virtualized
4040
rncli
4141
RNCLI
4242
CDNs
43-
haptics
43+
haptics
44+
async
45+
Podfile

docusaurus/docs/reactnative/contexts/message-input-context.mdx

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -244,17 +244,17 @@ const { sendMessage, toggleAttachmentPicker } = useMessageInputContext();
244244

245245
<SendMessage />
246246

247-
<!-- ### setInputRef -->
247+
{/* <!-- ### setInputRef --> */}
248248

249-
<!-- ### setQuotedMessageState -->
249+
{/* <!-- ### setQuotedMessageState --> */}
250250

251251
### `appendText`
252252

253253
<AppendText />
254254

255-
<!-- ### asyncIds -->
255+
{/* <!-- ### asyncIds --> */}
256256

257-
<!-- ### asyncUploads -->
257+
{/* <!-- ### asyncUploads --> */}
258258

259259
### closeAttachmentPicker
260260

@@ -288,9 +288,9 @@ const { sendMessage, toggleAttachmentPicker } = useMessageInputContext();
288288

289289
<NumberOfUploads />
290290

291-
<!-- ### onChange -->
291+
{/* <!-- ### onChange --> */}
292292

293-
<!-- ### onSelectItem -->
293+
{/* <!-- ### onSelectItem --> */}
294294

295295
### openAttachmentPicker
296296

@@ -308,7 +308,7 @@ const { sendMessage, toggleAttachmentPicker } = useMessageInputContext();
308308

309309
<OpenMentionsPicker />
310310

311-
<!-- ### pickFile -->
311+
{/* <!-- ### pickFile --> */}
312312

313313
### `removeFile`
314314

@@ -326,17 +326,17 @@ const { sendMessage, toggleAttachmentPicker } = useMessageInputContext();
326326

327327
<SelectedPicker />
328328

329-
<!-- ### sending -->
329+
{/* <!-- ### sending --> */}
330330

331-
<!-- ### sendMessageAsync -->
331+
{/* <!-- ### sendMessageAsync --> */}
332332

333333
### sendThreadMessageInChannel
334334

335335
<SendThreadMessageInChannel />
336336

337-
<!-- ### setAsyncIds -->
337+
{/* <!-- ### setAsyncIds --> */}
338338

339-
<!-- ### setAsyncUploads -->
339+
{/* <!-- ### setAsyncUploads --> */}
340340

341341
### setFileUploads
342342

docusaurus/docs/reactnative/guides/date-time-formatting.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ In this guide we will learn how date a time formatting can be customized within
77

88
## SDK components displaying date & time
99

10-
The following components provided by the SDK display datetime:
10+
The following components provided by the SDK display date time:
1111

1212
- `ChannelPreviewStatus` - Component showing last message date and time in `ChannelList`.
1313
- `ImageGalleryHeader` - Component showing the header in the `ImageGallery`.
@@ -19,7 +19,7 @@ The following components provided by the SDK display datetime:
1919

2020
## Format Customization
2121

22-
The datetime format can be customized by providing date format through the `i18n` JSON.
22+
The date time format can be customized by providing date format through the `i18n` JSON.
2323

2424
### Date & time formatting with i18n service
2525

@@ -31,7 +31,7 @@ Formatting via i18n service allows for SDK wide configuration. The configuration
3131
- Allows for high re-usability - apply the same configuration in multiple places via the same translation key.
3232
- Allows for custom formatting logic.
3333

34-
The default datetime formatting configuration is stored in the JSON translation files. The default translation keys are namespaced with prefix `timestamp/` followed by the component name. For example, the message date formatting can be targeted via `timestamp/MessageTimestamp`, because the underlying component is called `MessageTimestamp`.
34+
The default date time formatting configuration is stored in the JSON translation files. The default translation keys are namespaced with prefix `timestamp/` followed by the component name. For example, the message date formatting can be targeted via `timestamp/MessageTimestamp`, because the underlying component is called `MessageTimestamp`.
3535

3636
We can apply custom configuration in all the translation JSON files. It could look similar to the following example key-value pair.
3737

@@ -79,11 +79,11 @@ Let's dissect the example:
7979

8080
**Params**:
8181

82-
- `calendar` - This is a boolean field to decide if the date format should be in calendar format or not. The default value is `false`.
82+
- `calendar` - This is a `Boolean` field to decide if the date format should be in calendar format or not. The default value is `false`.
8383
- `calendarFormats` - This is an object that contains the formats for the calendar. The default value is `{ sameDay: 'LT', nextDay: 'LT', nextWeek: 'dddd', lastDay: 'dddd', lastWeek: 'dddd', sameElse: 'L' }`.
8484
- `format` - This is a string that contains the format of the date.
8585

86-
If calendar formatting is enabled, the dates are formatted with time-relative words ("yesterday at ...", "last ..."). The calendar strings can be further customized with `calendarFormats` object. The `calendarFormats` object has to cover all the formatting cases as shows the example below:
86+
If calendar formatting is enabled, the dates are formatted with time-relative words (`"yesterday at ..."`, `"last ..."`). The calendar strings can be further customized with `calendarFormats` object. The `calendarFormats` object has to cover all the formatting cases as shows the example below:
8787

8888
```js
8989
{
@@ -106,7 +106,7 @@ If `calendar` formatting is enabled, the `format` prop would be ignored. So to a
106106
The described rules follow the formatting rules required by the i18n library used under the hood - `i18next`. You can learn more about the rules in [the formatting section of the `i18next` documentation](https://www.i18next.com/translation-function/formatting#basic-usage).
107107
:::
108108

109-
### Custom datetime formatter functions
109+
### Custom date time formatter functions
110110

111111
Besides overriding the configuration parameters, we can override the default `timestampFormatter` function by providing custom `Streami18n` instance:
112112

0 commit comments

Comments
 (0)