-
Notifications
You must be signed in to change notification settings - Fork 10
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
docs: remove spinner + reduce load time + add rowDataMapper - PTL-1517 #2042
Changes from 1 commit
12d8121
a71d87d
87d4024
30c1c54
a1c2c36
1b80a8e
1279f56
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -208,6 +208,21 @@ Some **resource** attributes are `DATASERVER` or `REQUEST_SERVER` specific, whil | |||||
<grid-pro-server-side-datasource view-number="2"> | ||||||
``` | ||||||
|
||||||
</td> | ||||||
</tr> | ||||||
<tr> | ||||||
<td><code>:rowDataMapper</code></td> | ||||||
<td><code>Function</code></td> | ||||||
<td>Function to map the row data before it is sent to the grid. The function should return an array of objects, where each object represents a row in the grid.</td> | ||||||
<td> | ||||||
|
||||||
```html | ||||||
matteematt marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
<grid-pro-client-side-datasource | ||||||
:rowDataMapper="${(data) => data.map((row) => ({ ...row, calculatedValue: row.value1 + row.value2 }))}"> | ||||||
<grid-pro-server-side-datasource | ||||||
:rowDataMapper="${(data) => data.map((row) => ({ ...row, calculatedValue: row.value1 + row.value2 }))}"> | ||||||
``` | ||||||
|
||||||
</td> | ||||||
</tr> | ||||||
</tbody> | ||||||
|
@@ -334,14 +349,15 @@ Some **resource** attributes are `DATASERVER` or `REQUEST_SERVER` specific, whil | |||||
</td> | ||||||
</tr> | ||||||
<tr> | ||||||
<td><code>request</code></td> | ||||||
<td><code>string</code></td> | ||||||
<td><code>:request</code></td> | ||||||
<td><code>any</code></td> | ||||||
<td>Similar to <code>fields</code> but for <a href="/develop/server-capabilities/snapshot-queries-request-server/">Request Server</a> scenarios. This optional parameter enables you to specify request fields, which can include wildcards.</td> | ||||||
<td> | ||||||
|
||||||
```html | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Now we're adding template strings I think typescript syntax works better
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||||||
<grid-pro-client-side-datasource request="Trade.*"> | ||||||
<grid-pro-server-side-datasource request="Position.*,Price.*"> | ||||||
<grid-pro-client-side-datasource :request="Trade.*"> | ||||||
<grid-pro-server-side-datasource :request="Position.*,Price.*"> | ||||||
<grid-pro-client-side-datasource :request="${() => ({ TRADE_ID: '00001' })}"> | ||||||
``` | ||||||
|
||||||
</td> | ||||||
|
@@ -354,7 +370,7 @@ Some **resource** attributes are `DATASERVER` or `REQUEST_SERVER` specific, whil | |||||
|
||||||
```html | ||||||
<grid-pro-client-side-datasource request-auto-setup> | ||||||
<grid-pro-server-side-datasource request-auto-setup="true"> | ||||||
<grid-pro-server-side-datasource request-auto-setup=> | ||||||
``` | ||||||
|
||||||
</td> | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are you certain that this speed is ok? I set it to 2000 because I was testing on 1000 and sometimes it didn't load correctly? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it never failed for me.. @matteematt can you re-check this branch? let me know if it fails |
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.
This is very useful, thanks. However to be very nitpicky, in every other doc we've created a seperate table for properties just so it's super clear to use the
:
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.
addressed in a71d87d