playbook_ui_docs 15.6.0.pre.alpha.play266913088 → 15.6.0.pre.rc.0

data/app/pb_kits/playbook/pb_dropdown/docs/_dropdown_quickpick_range_end_rails.html.erb

@@ -1,19 +0,0 @@
-
-<%= pb_rails("dropdown", props: {
-  id: "date-range-quickpick-end-today",
-  label: "Date Range", 
-  variant: "quickpick", 
-  range_ends_today: true 
-}) %>
-
-<script>
-  document.addEventListener("DOMContentLoaded", () => {
-    const dropdown = document.getElementById("date-range-quickpick-end-today");
-    if (dropdown) {
-      dropdown.addEventListener("pb:dropdown:selected", (e) => {
-        const option = e.detail;
-        console.log("Selected option:", option);
-      });
-    }
-  });
-</script>

data/app/pb_kits/playbook/pb_dropdown/docs/_dropdown_quickpick_range_end_rails.md

@@ -1 +0,0 @@
-The optional `range_ends_today` prop can be used with the `quickpick` variant to set end date on all ranges that start with 'this' to today's date. For instance, by default 'This Year' will set end day to 12/31/(current year), but if `range_ends_today` prop is used, end date on that range will be today's date.

data/app/pb_kits/playbook/pb_dropdown/docs/_dropdown_quickpick_with_date_pickers_default_rails.html.erb

@@ -1,30 +0,0 @@
-<%= pb_rails("dropdown", props: {
-  id: "dropdown-quickpick-with-date-pickers-default",
-  label: "Date Range",
-  name: "date_range",
-  margin_bottom: "sm",
-  variant: "quickpick",
-  default_value: "This Month",
-  controls_start_id: "start-date-picker-default",
-  controls_end_id: "end-date-picker-default",
-  start_date_id: "quickpick_start_date_default",
-  start_date_name: "start_date",
-  end_date_id: "quickpick_end_date_default",
-  end_date_name: "end_date"
-}) %>
-
-<%= pb_rails("date_picker", props: {
-  picker_id: "start-date-picker-default",
-  label: "Start Date",
-  name: "start_date_picker",
-  placeholder: "Select Start Date",
-  sync_start_with: "dropdown-quickpick-with-date-pickers-default"
-}) %>
-
-<%= pb_rails("date_picker", props: {
-  picker_id: "end-date-picker-default",
-  label: "End Date",
-  name: "end_date_picker",
-  placeholder: "Select End Date",
-  sync_end_with: "dropdown-quickpick-with-date-pickers-default"
-}) %>

data/app/pb_kits/playbook/pb_dropdown/docs/_dropdown_quickpick_with_date_pickers_default_rails.md

@@ -1,3 +0,0 @@
-This example demonstrates the 3-input pattern with a default value. The dropdown is initialized with "This Month" selected, and both DatePickers are automatically populated with the corresponding start and end dates.
-
-The default value can be set using the `default_value` prop with any of the quickpick option labels.

data/app/pb_kits/playbook/pb_dropdown/docs/_dropdown_quickpick_with_date_pickers_rails.html.erb

@@ -1,29 +0,0 @@
-<%= pb_rails("dropdown", props: {
-  id: "dropdown-quickpick-with-date-pickers",
-  label: "Date Range",
-  name: "date_range",
-  margin_bottom: "sm",
-  variant: "quickpick",
-  controls_start_id: "start-date-picker",
-  controls_end_id: "end-date-picker",
-  start_date_id: "quickpick_start_date",
-  start_date_name: "start_date",
-  end_date_id: "quickpick_end_date",
-  end_date_name: "end_date"
-}) %>
-
-<%= pb_rails("date_picker", props: {
-  picker_id: "start-date-picker",
-  label: "Start Date",
-  name: "start_date_picker",
-  placeholder: "Select Start Date",
-  sync_start_with: "dropdown-quickpick-with-date-pickers"
-}) %>
-
-<%= pb_rails("date_picker", props: {
-  picker_id: "end-date-picker",
-  label: "End Date",
-  name: "end_date_picker",
-  placeholder: "Select End Date",
-  sync_end_with: "dropdown-quickpick-with-date-pickers"
-}) %>

data/app/pb_kits/playbook/pb_dropdown/docs/_dropdown_quickpick_with_date_pickers_rails.md

@@ -1,13 +0,0 @@
-The quickpick variant can be synced with two DatePickers for a 3-input pattern. When a quickpick option is selected from the dropdown, both DatePickers are automatically populated. When either DatePicker is manually changed, the dropdown is cleared.
-
-#### Props for 3-Input Pattern:
-
-- `controls_start_id` - ID of the start DatePicker to sync with
-- `controls_end_id` - ID of the end DatePicker to sync with
-
-#### DatePicker Props:
-
-- `sync_start_with` - ID of the dropdown to clear when start date changes
-- `sync_end_with` - ID of the dropdown to clear when end date changes
-
-This pattern allows users to quickly select common date ranges or manually pick specific dates.

data/app/pb_kits/playbook/pb_multiple_users/docs/_multiple_users_with_tooltip.jsx

@@ -1,42 +0,0 @@
-import React from 'react'
-import MultipleUsers from '../../pb_multiple_users/_multiple_users'
-
-const MultipleUsersWithTooltip = (props) => {
-    return (
-        <div>
-            <MultipleUsers
-                users={[
-                    {
-                        name: 'Patrick Welch',
-                        imageUrl: 'https://randomuser.me/api/portraits/men/9.jpg',
-                        tooltip: "Patrick Welch - Online"
-                    },
-                    {
-                        name: 'Lucille Sanchez',
-                        imageUrl: 'https://randomuser.me/api/portraits/women/6.jpg',
-                        tooltip: "Lucille Sanchez - Offline"
-                    },
-                    {
-                        name: 'Beverly Reyes',
-                        imageUrl: 'https://randomuser.me/api/portraits/women/74.jpg',
-                        tooltip: "Beverly Reyes - Online"
-                    },
-                    {
-                        name: 'Keith Craig',
-                        imageUrl: 'https://randomuser.me/api/portraits/men/40.jpg',
-                        tooltip: "Keith Craig - Away"
-                    },
-                    {
-                        name: 'Alicia Cooper',
-                        imageUrl: 'https://randomuser.me/api/portraits/women/46.jpg',
-                        tooltip: "Alicia Cooper - Busy"
-                    },
-                ]}
-                withTooltip
-                {...props}
-            />
-        </div>
-    )
-}
-``
-export default MultipleUsersWithTooltip

data/app/pb_kits/playbook/pb_multiple_users/docs/_multiple_users_with_tooltip.md

@@ -1 +0,0 @@
-Use the `withTooltip` boolean prop to enable setting user-specific tooltip content via the `tooltip` property in the users array.

data/app/pb_kits/playbook/pb_select/docs/_select_input_options.html.erb

@@ -1,16 +0,0 @@
-<%= pb_rails("select", props: {
-  label: "Favorite Food",
-  name: "favorite_food",
-  options: [
-    { value: "pizza", value_text: "Pizza" },
-    { value: "tacos", value_text: "Tacos" },
-    { value: "sushi", value_text: "Sushi" }
-  ],
-  input_options: {
-    'aria-label': "Select your favorite food",
-    class: "custom-select-class",
-    data: { controller: "search", action: "change->search#filter" },
-    id: "favorite-food-select"
-  }
-}) %>
-

data/app/pb_kits/playbook/pb_select/docs/_select_input_options.jsx

@@ -1,30 +0,0 @@
-import React from 'react'
-
-import Select from '../_select'
-
-const SelectInputOptions = (props) => {
-  const options = [
-    { value: 'pizza', text: 'Pizza' },
-    { value: 'tacos', text: 'Tacos' },
-    { value: 'sushi', text: 'Sushi' },
-  ]
-
-  return (
-    <>
-      <Select
-          inputOptions={{
-            'aria-label': 'Select your favorite food',
-            className: 'custom-select-class',
-            id: 'favorite-food-select',
-          }}
-          label="Favorite Food"
-          name="favorite_food"
-          options={options}
-          {...props}
-      />
-    </>
-  )
-}
-
-export default SelectInputOptions
-

data/app/pb_kits/playbook/pb_select/docs/_select_input_options.md

@@ -1 +0,0 @@
-Use the `input_options` / `inputOptions` prop to pass additional attributes directly to the underlying `<select>` element instead of the outer wrapper. This is useful for applying data attributes, custom IDs, or other HTML attributes that need to be on the select element itself.

data/app/pb_kits/playbook/pb_table/docs/_table_with_filter_variant.jsx

@@ -1,134 +0,0 @@
-import React, { useState } from "react"
-import { Button, Date as DateKit, DatePicker, Dropdown, Select, Table, TextInput, Typeahead, Flex } from "playbook-ui"
-
- // Mock Data for Table  
-  const users = [
-    { id: 1, name: "Jennifer", title: "Associate Scrum Master", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-01" },
-    { id: 2, name: "Nick", title: "UX Engineer II", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-02" },
-    { id: 3, name: "Nida", title: "Senior UX Engineer", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-03" },
-    { id: 4, name: "Justin", title: "Director of User Experience Engineering", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-04" },
-    { id: 5, name: "Edward", title: "UX Designer II", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-05" },
-    { id: 6, name: "Elisa", title: "UX Engineer", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-06" },
-    { id: 7, name: "Gary", title: "UX Engineer", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-07" },
-    { id: 8, name: "Barkley", title: "Nitro Quality Ninja", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-08" },
-    { id: 9, name: "Aaron", title: "Associate Nitro Quality Ninja", department: "Business Technology", branch: "Philadelphia", startDate: "2025-01-09" },
-  ]
-
-const TableWithFilterVariant = () => {
-  const [territory, setTerritory] = useState("")
-
-  // --------Filter content example ------
-  const filterContent = ({ closePopover }) => (
-          <>
-            <TextInput
-                label="Territory ID"
-                onChange={event => setTerritory(event.target.value)}
-                value={territory}
-            />
-
-            <Typeahead
-                label="Title"
-                options={[
-                  { key: "senior-ux-engineer", label: "Senior UX Engineer", value: "senior-ux-engineer" },
-                  { key: "ux-engineer", label: "UX Engineer", value: "ux-engineer" },
-                  { key: "ux-designer", label: "UX Designer", value: "ux-designer" }
-                ]}
-            />
-
-            <Select
-                blankSelection="All Departments"
-                label="Department"
-                options={[
-                  { value: "Business Technology", label: "Business Technology", key: "business-technology" },
-                  { value: "Customer Development", label: "Customer Development", key: "customer-development" },
-                  { value: "Talent Acquisition", label: "Talent Acquisition", key: "talent-acquisition" }
-                ]}
-            />
-
-            <Dropdown
-                label="Branch"
-                options={[
-                  { key: "Philadelphia", label: "Philadelphia", value: "philadelphia" },
-                  { key: "New York", label: "New York", value: "new-york" },
-                  { key: "Austin", label: "Austin", value: "austin" }
-                ]}
-            />
-
-            <DatePicker
-                label="Start Date"
-                paddingY="sm"
-                pickerId="startedOn"
-            />
-            <Flex spacing="between">
-            <Button
-                onClick={() => {
-                  alert("No filtering functionality - just a pattern demo!")
-                  closePopover()
-                }}
-                text="Filter"
-            />
-            <Button
-                text="Defaults"
-                variant="secondary"
-            />
-            </Flex>
-          </>
-        )
-  // -------End Filter content example ------
-  
-  return (
-    <Table 
-        filterContent={filterContent}
-        filterProps={{
-          results: 50,
-          sortOptions: {
-            territory_id: "Territory ID",
-            first_name: "Name",
-            started_on: "Start Date",
-            department_name: "Department",
-            title_name: "Title",
-            branch_branch_name: "Branch",
-          },
-          sortValue: [{ name: 'started_on', dir: 'asc' }],
-        }}
-        title="Table Title Here"
-        variant="withFilter"
-    >
-      <Table.Head>
-        <Table.Row>
-          <Table.Header>{'Territory ID'}</Table.Header>
-          <Table.Header>{'Name'}</Table.Header>
-          <Table.Header>{'Title'}</Table.Header>
-          <Table.Header>{'Department'}</Table.Header>
-          <Table.Header>{'Branch'}</Table.Header>
-          <Table.Header textAlign="right">{'Start Date'}</Table.Header>
-        </Table.Row>
-      </Table.Head>
-      <Table.Body>
-        {users.map((user) => (
-          <Table.Row key={user.id}>
-            <Table.Cell 
-                marginX={{ xs: "sm" }}
-                numberSpacing="tabular"
-            >
-                {user.id}
-            </Table.Cell>
-            <Table.Cell marginX={{ xs: "sm" }}>{user.name}</Table.Cell>
-            <Table.Cell marginX={{ xs: "sm" }}>{user.title}</Table.Cell>
-            <Table.Cell marginX={{ xs: "sm" }}>{user.department}</Table.Cell>
-            <Table.Cell marginX={{ xs: "sm" }}>{user.branch}</Table.Cell>
-            <Table.Cell marginX={{ xs: "sm" }}>
-              <DateKit 
-                  alignment="right"
-                  showCurrentYear
-                  value={user.startDate}
-              />
-            </Table.Cell>
-          </Table.Row>
-        ))}
-      </Table.Body>
-    </Table>
-  )
-}
-
-export default TableWithFilterVariant

data/app/pb_kits/playbook/pb_table/docs/_table_with_filter_variant.md

@@ -1,34 +0,0 @@
-Set the `variant` prop to `withFilter` to render a Table with a filter. The variant automatically handles:
-
-- Card wrapper with standard responsive margins
-- Optional `title` prop to render title above the card
-- Filter component rendering with Design defaults
-- SectionSeparator between filter and table
-- Flex layout for proper alignment
-
-#### Required Props
-
-- `variant="withFilter"`: Enables the filter variant
-- `filterContent`: A function that receives `{ closePopover }` and returns the filter's body content (inputs, buttons, etc.). Use this to pass in all input kits, etc needed inside the Filter itself.
-- `filterProps`: An object containing Filter-specific props like `results`, `sortOptions`, `sortValue`, etc.
-
-#### Optional Props
-
-- `title`: Displays a title above the card
-- All standard Table props (`size`, `collapse`, etc.) can be used, but defaults are already set to match Design guidelines
-- All standard Filter props can be used, but defaults are already set to match Design guidelines.
-
-#### Default Filter Props
-
-The Table kit automatically sets these Filter defaults (which you can override via `filterProps`):
-
-- `background={false}`
-- `maxHeight="50vh"`
-- `minWidth="xs"`
-- `popoverProps={{ width: "350px" }}`
-
-
-**IMPORTANT NOTE**: 
-The purpose of this variant is to provide an easy way to set up a Table with a Filter with Design standards applied by default.
-
-If you are looking for more customization than this embedded variant provides, you may be better served by using the individual kits as demonstrated in our Table Filter Card Building Block [here](https://playbook.powerapp.cloud/building_blocks/table_filter_card/react).

data/app/pb_kits/playbook/pb_table/docs/_table_with_filter_variant_rails.html.erb

@@ -1,101 +0,0 @@
-    <% users = [
-        { id: 1, name: "Jennifer", title: "Associate Scrum Master", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 1) },
-        { id: 2, name: "Nick", title: "UX Engineer II", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 2) },
-        { id: 3, name: "Nida", title: "Senior UX Engineer", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 3) },
-        { id: 4, name: "Justin", title: "Director of User Experience Engineering", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 4) },
-        { id: 5, name: "Edward", title: "UX Designer II", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 5) },
-        { id: 6, name: "Elisa", title: "UX Engineer", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 6) },
-        { id: 7, name: "Gary", title: "UX Engineer", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 7) },
-        { id: 8, name: "Barkley", title: "Nitro Quality Ninja", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 8) },
-        { id: 9, name: "Aaron", title: "Associate Nitro Quality Ninja", department: "Business Technology", branch: "Philadelphia", start_date: Date.new(2025, 1, 9) },
-    ] %>
-
-<% filter_content = 
-    pb_rails("text_input", props: {
-      label: "Territory ID",
-      placeholder: "Enter Territory ID"
-    }) +
-    pb_rails("typeahead", props: {
-      label: "Title",
-      options: [
-        { label: "Senior UX Engineer", value: "senior-ux-engineer" },
-        { label: "UX Engineer", value: "ux-engineer" },
-        { label: "UX Designer", value: "ux-designer" }
-      ]
-    }) +
-    pb_rails("select", props: {
-      blank_selection: "All Departments",
-      label: "Department",
-      options: [
-        { value: "Business Technology", text: "Business Technology" },
-        { value: "Customer Development", text: "Customer Development" },
-        { value: "Talent Acquisition", text: "Talent Acquisition" }
-      ]
-    }) +
-    pb_rails("dropdown", props: {
-      label: "Branch",
-      options: [
-        { label: "Philadelphia", value: "philadelphia" },
-        { label: "New York", value: "new-york" },
-        { label: "Austin", value: "austin" }
-      ]
-    }) +
-    pb_rails("date_picker", props: {
-      label: "Start Date",
-      padding_y: "sm",
-      picker_id: "startedOn"
-    }) +
-    pb_rails("flex", props: { spacing: "between" }) do
-      pb_rails("button", props: {
-        text: "Filter",
-      }) +
-      pb_rails("button", props: {
-        text: "Defaults",
-        variant: "secondary"
-      })
-    end
-%>
-
-<%= pb_rails("table", props: {
-  variant: "with_filter",
-  title: "Table Title Here",
-  filter_content: filter_content,
-  filter_props: {
-    id: "user-table-filters-1",
-    results: 9,
-    sort_menu: [
-        { item: "Start Date", link: "?q[sorts]=started_on+asc", active: true, direction: "asc" },
-        { item: "First Name", link: "?q[sorts]=name+asc", active: false },
-        { item: "Title", link: "?q[sorts]=title+asc", active: false },
-        { item: "Department", link: "?q[sorts]=department+asc", active: false },
-        { item: "Branch", link: "?q[sorts]=branch+asc", active: false },
-        { item: "Territory ID", link: "?q[sorts]=territory_id+asc", active: false },
-    ],
-  }
-}) do %>
-  <%= pb_rails("table/table_head") do %>
-    <%= pb_rails("table/table_row") do %>
-      <%= pb_rails("table/table_header", props: { text: "Territory ID" }) %>
-      <%= pb_rails("table/table_header", props: { text: "Name" }) %>
-      <%= pb_rails("table/table_header", props: { text: "Title" }) %>
-      <%= pb_rails("table/table_header", props: { text: "Department" }) %>
-      <%= pb_rails("table/table_header", props: { text: "Branch" }) %>
-      <%= pb_rails("table/table_header", props: { text: "Start Date", text_align: "right" }) %>
-    <% end %>
-  <% end %>
-
-  <%= pb_rails("table/table_body") do %>
-    <% users.each do |user| %>
-      <%= pb_rails("table/table_row") do %>
-        <%= pb_rails("table/table_cell", props: { margin_x: { xs: "sm" }, number_spacing: "tabular" }) { user[:id].to_s } %>
-        <%= pb_rails("table/table_cell", props: { margin_x: { xs: "sm" } }) { user[:name] } %>
-        <%= pb_rails("table/table_cell", props: { margin_x: { xs: "sm" } }) { user[:title] } %>
-        <%= pb_rails("table/table_cell", props: { margin_x: { xs: "sm" } }) { user[:department] } %>
-        <%= pb_rails("table/table_cell", props: { margin_x: { xs: "sm" } }) { user[:branch] } %>
-        <%= pb_rails("table/table_cell", props: { margin_x: { xs: "sm" } }) do %>
-           <%= pb_rails("date", props: {alignment: "right", date: user[:start_date].to_s, show_current_year: true } ) %>        
-        <% end %>
-      <% end %>
-    <% end %>
-  <% end %>
-<% end %>

data/app/pb_kits/playbook/pb_table/docs/_table_with_filter_variant_rails.md

@@ -1,33 +0,0 @@
-Set the `variant` prop to `with_filter` to render a Table with a filter. The variant automatically handles:
-
-- Card wrapper with standard responsive margins
-- Optional `title` prop to render title above the card
-- Filter component rendering with Design defaults
-- SectionSeparator between filter and table
-- Flex layout for proper alignment
-
-#### Required Props
-
-- `variant: "with_filter"`: Enables the filter variant
-- `filter_content`: The filter's body content (inputs, buttons, etc.) built with `pb_rails` string concatenation
-- `filter_props`: A hash containing Filter-specific props like `results`, `sort_menu`, etc.
-
-#### Optional Props
-
-- `title`: Displays a title above the card
-- All standard Table props (`size`, `collapse`, etc.) can be used, but defaults are already set to match Design guidelines
-
-#### Default Filter Props
-
-The Table kit automatically sets these Filter defaults (which you can override via `filter_props`):
-
-- `background: false`
-- `max_height: "50vh"`
-- `min_width: "xs"`
-- `popover_props: { width: "350px" }`
-
-
-**IMPORTANT NOTE**: 
-The purpose of this variant is to provide an easy way to set up a Table with a Filter with Design standards applied by default.
-
-If you are looking for more customization than this embedded variant provides, you may be better served by using the individual kits as demonstrating in our Table Filter Card Building Block as seen [here](https://playbook.powerapp.cloud/building_blocks/table_filter_card/rails).