Fix issue #300: changing pagination button text

dash_table/DataTable.py

@@ -313,7 +313,7 @@ class DataTable(Component):
 - page_action (a value equal to: 'custom', 'native', 'none'; optional): `page_action` refers to a mode of the table where
 not all of the rows are displayed at once: only a subset
 are displayed (a "page") and the next subset of rows
-can viewed by clicking "Next" or "Previous" buttons
+can viewed by clicking "<" (previous) or ">" (next) buttons
 at the bottom of the page.
 
 Pagination is used to improve performance: instead of
@@ -323,7 +323,7 @@ class DataTable(Component):
 With pagination, we can either page through data that exists
 in the table (e.g. page through `10,000` rows in `data` `100` rows at a time)
 or we can update the data on-the-fly with callbacks
-when the user clicks on the "Previous" or "Next" buttons.
+when the user clicks on the "<" (previous) or ">" (next) buttons.
 These modes can be toggled with this `page_action` parameter:
 - `'native'`: all data is passed to the table up-front, paging logic is
 handled by the table

dash_table/metadata.json

@@ -750,7 +750,7 @@
           ]
         },
         "required": false,
-        "description": "`page_action` refers to a mode of the table where\nnot all of the rows are displayed at once: only a subset\nare displayed (a \"page\") and the next subset of rows\ncan viewed by clicking \"Next\" or \"Previous\" buttons\nat the bottom of the page.\n\nPagination is used to improve performance: instead of\nrendering all of the rows at once (which can be expensive),\nwe only display a subset of them.\n\nWith pagination, we can either page through data that exists\nin the table (e.g. page through `10,000` rows in `data` `100` rows at a time)\nor we can update the data on-the-fly with callbacks\nwhen the user clicks on the \"Previous\" or \"Next\" buttons.\nThese modes can be toggled with this `page_action` parameter:\n- `'native'`: all data is passed to the table up-front, paging logic is\nhandled by the table\n- `'custom'`: data is passed to the table one page at a time, paging logic\nis handled via callbacks\n- `none`: disables paging, render all of the data at once",
+        "description": "`page_action` refers to a mode of the table where\nnot all of the rows are displayed at once: only a subset\nare displayed (a \"page\") and the next subset of rows\ncan viewed by clicking \"<\" (previous) or \">\" (next) buttons\nat the bottom of the page.\n\nPagination is used to improve performance: instead of\nrendering all of the rows at once (which can be expensive),\nwe only display a subset of them.\n\nWith pagination, we can either page through data that exists\nin the table (e.g. page through `10,000` rows in `data` `100` rows at a time)\nor we can update the data on-the-fly with callbacks\nwhen the user clicks on the \"<\" (previous) or \">\" (next) buttons.\nThese modes can be toggled with this `page_action` parameter:\n- `'native'`: all data is passed to the table up-front, paging logic is\nhandled by the table\n- `'custom'`: data is passed to the table one page at a time, paging logic\nis handled via callbacks\n- `none`: disables paging, render all of the data at once",
         "defaultValue": {
           "value": "'native'",
           "computed": false
@@ -1757,4 +1757,4 @@
       }
     }
   }
-}
+}

man/dashDataTable.Rd

@@ -361,7 +361,7 @@ and not have borders between the columns.}
 \item{pagination_mode}{A value equal to: 'fe', 'be', true, false. "pagination" refers to a mode of the table where
 not all of the rows are displayed at once: only a subset
 are displayed (a "page") and the next subset of rows
-can viewed by clicking "Next" or "Previous" buttons
+can viewed by clicking "<" (previous) or ">" (next) buttons
 at the bottom of the page.
 
 Pagination is used to improve performance: instead of
@@ -371,7 +371,7 @@ we only display a subset of them.
 With pagination, we can either page through data that exists
 in the table (e.g. page through `10,000` rows in `data` `100` rows at a time)
 or we can update the data on-the-fly with callbacks
-when the user clicks on the "Previous" or "Next" buttons.
+when the user clicks on the "<" (previous) or ">" (next) buttons.
 These modes can be toggled with this `pagination_mode` parameter:
 - `'fe'` refers to "front-end" paging: passing large data up-front
 - `'be'` refers to "back-end" paging: updating the data on the fly via callbacks
@@ -759,4 +759,3 @@ across all pages.}
 Subscribe to [https://github.com/plotly/dash-table/issues/168](https://github.com/plotly/dash-table/issues/168)
 for updates on the dropdown API.}
 }
-

src/dash-table/components/ControlledTable/index.tsx

@@ -796,8 +796,8 @@ export default class ControlledTable extends PureComponent<ControlledTableProps>
             </div>
             {!this.displayPagination ? null : (
                 <div>
-                    <button className='previous-page' onClick={this.loadPrevious}>Previous</button>
-                    <button className='next-page' onClick={this.loadNext}>Next</button>
+                    <button className='previous-page' onClick={this.loadPrevious}>&lt;</button>
+                    <button className='next-page' onClick={this.loadNext}>&gt;</button>
                 </div>
             )}
         </div>);

src/dash-table/dash/DataTable.js

@@ -557,7 +557,7 @@ export const propTypes = {
      * `page_action` refers to a mode of the table where
      * not all of the rows are displayed at once: only a subset
      * are displayed (a "page") and the next subset of rows
-     * can viewed by clicking "Next" or "Previous" buttons
+     * can viewed by clicking "<" (previous) or ">" (next) buttons
      * at the bottom of the page.
      *
      * Pagination is used to improve performance: instead of
@@ -567,7 +567,7 @@ export const propTypes = {
      * With pagination, we can either page through data that exists
      * in the table (e.g. page through `10,000` rows in `data` `100` rows at a time)
      * or we can update the data on-the-fly with callbacks
-     * when the user clicks on the "Previous" or "Next" buttons.
+     * when the user clicks on the "<" (previous) or ">" (next) buttons.
      * These modes can be toggled with this `page_action` parameter:
      * - `'native'`: all data is passed to the table up-front, paging logic is
      * handled by the table