playbook_ui_docs 12.25.0.pre.alpha.play824786 → 12.25.0.pre.alpha.railsmultilevelimprovements758

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 55a134041f0bd091d00782a4574c401246c42c819da44aeab2ea54f3c81bbdaf
-  data.tar.gz: b6f5c0a997ba59e6a056abcf4089e3c2e8be28a02d52267c36f3de0d3fe9cbce
+  metadata.gz: bcca33160c0d885863c0ed9e719532201be8e02be55dc2e446fcf8abea85bfb6
+  data.tar.gz: 3a27d6a9e1616040badcd6c56ea3c88e950684e6e2572b87dc34cdf599562a33
 SHA512:
-  metadata.gz: 42c74c97bc51212b2f2a509dd60776f783abedfa775f5b5026e7f3445fa74366d07d5b5a3d272454d6afb3ad3c494aa5122ee9c93dbac5dda3be39874e84fc3c
-  data.tar.gz: 671afc3e799488d9b4965607f20f7442efd7c203265ad41d403db96738a89af685a97730a82dba91fb73864b7828b1e7ddc1a9b0d8cafdb1872d24b912ed7588
+  metadata.gz: 577ba7cf091e2c15a0db1f358676b65c2b112e56dbc8a926f9cec949b327f23affb9d41eb1f16e5b80c33f0c011cc7b9124d4565624550699f9da368c77f9d67
+  data.tar.gz: d15e3d3f816b8ac3f15f8b745377a79e17a3f5e518bee47bf2af74977007d507d055a1881332bfec6d88b653ada032f2a54ab56af03650903b8a09e3d0b55676

data/app/pb_kits/playbook/pb_avatar/docs/_avatar_swift.md

@@ -1,82 +1 @@
-In the world of design, consistency is key. Whether you're designing a website, app, or product, having a consistent visual language can make all the difference. That's where design systems come in.
-
-A design system is a collection of reusable components, guidelines, and assets that help ensure consistency across all of your design work. It's a way to standardize your design language, making it easier for your team to work together and for your users to navigate your products.
-
-In this article, we'll explore the various elements of a design system and how they can be used to create a cohesive and effective design language.
-
-### Headings
-Headings are an essential component of any design system. They help organize content, provide visual hierarchy, and make it easier for users to scan and find what they're looking for. A good design system will have headings of various sizes, ranging from H1 (the largest) to H6 (the smallest). Here's an example:
-
-# H1: Main Title Headings
-## H2: Headings
-### H3: Subheadings
-#### H4: Sub-Subheadings
-
-![image for avatar](https://images.unsplash.com/photo-1684237276530-a562fa8338b1?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=580&q=80)
-
-### Lists
-Lists are another important component of a design system. They help organize content into easily digestible chunks, making it easier for users to read and understand. There are two types of lists: ordered and unordered.
-
-Ordered lists are numbered, and each item is listed in a specific order. For example:
-
-1. Headings
-2. Lists
-3. Blockquotes
-4. Links
-5. Bold
-6. Underline
-7. Code Blocks
-8. Inline Code
-9. Example Tables
-10. Horizontal Rules
-
-Unordered lists, on the other hand, use bullet points to separate each item. For example:
-
-* Headings
-* Lists
-* Blockquotes
-* Links
-* Bold
-* Underline
-* Code Blocks
-* Inline Code
-* Example Tables
-* Horizontal Rules
-
-### Blockquotes
-Blockquotes are used to highlight a particular section of text or quote. They’re often used to emphasize an important point or to provide context. Here’s an example:
-
-> “Design systems are a collection of reusable components, guidelines, and assets that help ensure consistency across all of your design work.” - ChatGPT
-
-
-### Links
-Links are an important part of any design system. They allow users to navigate between different pages and sections of your product. When using links in your design system, it’s important to make sure they’re consistent in color, size, and style. Here’s an example:
-Click here to learn more about design systems.
-
-### Bold, Underline, & Italics
-**Bold** and _underline_ are used to *highlight specific words* or phrases within ~~a block of~~ text. They help draw the user’s attention to important information. Here’s an example: *Design systems are* a collection of **reusable components**, **guidelines**, and **assets** that help ensure _consistency across all of your design work_.
-
-### Code Blocks and Inline Code
-Code blocks and `inline code` are used to display and highlight code within a block of text. This is especially useful for developers who need to reference code snippets in their work. 
-
-Here’s an example:
-
-```js
-function greet() {
-	console.log(“Hello, world!”);
-}
-```
-
-### Example Tables
-Example tables are used to display data in a clear and organized way. They help users compare and analyze information quickly. Here’s an example:
-
-| Tables   |      Are      |  Cool |
-|----------|:-------------:|------:|
-| col 1 is |  left-aligned | $1600 |
-| col 2 is |    centered   |   $12 |
-| col 3 is | right-aligned |    $1 |
-
----
-
-### Horizontal Rules
-Horizontal rules are used to separate sections of content visually. They help break up long blocks of text and make it easier for users
+![image for avatar](https://images.unsplash.com/photo-1684237276530-a562fa8338b1?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D&auto=format&fit=crop&w=580&q=80)

data/app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_default.html.erb

@@ -64,9 +64,9 @@
   }] %>
 
 
-<%= pb_rails("multi_level_select", props: {
-    id: "default-multi-level-select",
-    tree_data:treeData
-    }) %>
+  <%= pb_rails("multi_level_select", props: {
+      id: "default-multi-level-select",
+      tree_data:treeData
+  }) %>
 
 

data/app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_default.md

@@ -2,4 +2,4 @@ The MultiLevelSelect kit renders a multi leveled select dropdown based on data f
 
 For the React version of the kit, the `onSelect` prop returns an array of all checked items, irrespective of whether it is a parent, child or grandchild. Open the console on this example and check and uncheck checkboxes to see this is action!
 
-For the Rails version, the array of checked items is attached to the DOM in a data attribute titled `data-tree` on the wrapping div around  the MultiLevelSelect.
+For the Rails version, the array of checked items is attached to the DOM in a data attribute titled `data-tree` on the wrapping div around the MultiLevelSelect.

data/app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_return_all_selected.html.erb

@@ -3,7 +3,6 @@
     value: "Power Home Remodeling",
     id: "powerhome1",
     expanded: true,
-
     children: [
       {
         label: "People",

data/app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_with_form.html.erb

@@ -0,0 +1,72 @@
+<%= pb_form_with(scope: :example, url: "", method: :get) do |form| %>
+
+  <% treeData = [{
+  label: "Power Home Remodeling",
+  value: "Power Home Remodeling",
+  id: "powerhome1",
+  expanded: true,
+  children: [
+    {
+      label: "People",
+      value: "People",
+      id: "people1",
+      children: [
+        {
+          label: "Talent Acquisition",
+          value: "Talent Acquisition",
+          id: "talent1",
+        },
+        {
+          label: "Business Affairs",
+          value: "Business Affairs",
+          id: "business1",
+          children: [
+            {
+              label: "Initiatives",
+              value: "Initiatives",
+              id: "initiative1",
+            },
+            {
+              label: "Learning & Development",
+              value: "Learning & Development",
+              id: "development1",
+            },
+          ],
+        },
+        {
+          label: "People Experience",
+          value: "People Experience",
+          id: "experience1",
+        },
+      ],
+    },
+    {
+      label: "Contact Center",
+      value: "Contact Center",
+      id: "contact1",
+      children: [
+        {
+          label: "Appointment Management",
+          value: "Appointment Management",
+          id: "appointment1",
+        },
+        {
+          label: "Customer Service",
+          value: "Customer Service",
+          id: "customer1",
+        },
+        {
+          label: "Energy",
+          value: "Energy",
+          id: "energy1",
+        },
+      ],
+    },
+  ],
+}] %>
+
+  <%= form.multi_level_select :example, props: {id: "with-form-multi-level-select", tree_data: treeData, return_all_selected: true } %>
+  <%= form.actions do |action| %>
+    <%= action.button props: { type: "submit", text: "Submit", variant: "primary", margin_top: "lg" } %>
+  <% end %>   
+<% end %>

data/app/pb_kits/playbook/pb_multi_level_select/docs/example.yml

@@ -2,6 +2,7 @@ examples:
   rails:
   - multi_level_select_default: Default
   - multi_level_select_return_all_selected: Return All Selected
+  - multi_level_select_with_form: With Form
   
   react:
   - multi_level_select_default: Default

data/app/pb_kits/playbook/pb_phone_number_input/docs/example.yml

@@ -5,11 +5,9 @@ examples:
   - phone_number_input_preferred_countries: Preferred Countries
   - phone_number_input_initial_country: Initial Country
   - phone_number_input_only_countries: Limited Countries
-  - phone_number_input_validation: Form Validation
 
   rails:
   - phone_number_input_default: Default
   - phone_number_input_preferred_countries: Preferred Countries
   - phone_number_input_initial_country: Initial Country
-  - phone_number_input_only_countries: Limited Countries
-  - phone_number_input_validation: Form Validation
+  - phone_number_input_only_countries: Limited Countries

data/app/pb_kits/playbook/pb_phone_number_input/docs/index.js

@@ -2,4 +2,3 @@ export { default as PhoneNumberInputDefault } from './_phone_number_input_defaul
 export { default as PhoneNumberInputPreferredCountries } from './_phone_number_input_preferred_countries'
 export { default as PhoneNumberInputInitialCountry } from './_phone_number_input_initial_country'
 export { default as PhoneNumberInputOnlyCountries } from './_phone_number_input_only_countries'
-export { default as PhoneNumberInputValidation } from './_phone_number_input_validation'

data/dist/app/components/playbook/pb_docs/kit_api.html.erb

@@ -7,7 +7,7 @@
           <%= pb_rails("nav/item", props: { text: "Global Props", link: "#", active: true, dark: dark }) %>
         <% end %>
       <% end %>
-      <%= pb_rails("section_separator", props:{ dark: dark }) %>
+      <%= pb_rails("section_separator", dark: dark) %>
       <%= pb_rails("card/card_body", props: {}) do %>
         <%= pb_rails("table", props: {container: false, disable_hover: true, dark: dark }) do %>
           <thead>

data/dist/app/components/playbook/pb_docs/kit_example.html.erb

@@ -1,21 +1,15 @@
 <% example_html = ERB.new(example).result %>
 
 <%= pb_rails("card", props: { classname: "pb--doc", padding: "none", dark: dark }) do %>
-  <% unless (action_name == "kit_show_swift") %>
-    <div class="pb--kit-example">
-      <%= pb_rails("caption", props: { text: example_title, dark: dark }) %>
-      <br />
-      <%= example %>
-      <br>
-    </div>
-  <% else %>
-    <div class="pb--kit-example-markdown pt_none markdown <%= dark ? "dark" : "" %>">
-      <%= pb_rails("caption", props: { text: example_title, dark: dark, margin_top: "md" }) %>
-      <%= render_markdown(description) %>
-    </div>
-  <% end %>
+  <div class="pb--kit-example">
+    <%= pb_rails("caption", props: { text: example_title, dark: dark }) %>
+    <br />
+    <%= example %>
+    <br>
+  </div>
+
   <% if show_code %>
-    <div class="markdown pb--kit-example-markdown markdown <%= dark ? "dark" : "" %>">
+    <div class="markdown pb--kit-example-markdown <%= dark ? "dark" : "" %>">
       <%= render_markdown(description) %>
     </div>
     <div id="code-wrapper">

data/dist/app/components/playbook/pb_docs/kit_example.rb

@@ -8,7 +8,7 @@ module Playbook
       prop :example_title, type: Playbook::Props::String, required: true
       prop :example_key, type: Playbook::Props::String, required: true
       prop :show_code, type: Playbook::Props::Boolean, default: true
-      prop :type, type: Playbook::Props::Enum, values: %w[rails react swift], default: "rails"
+      prop :type, type: Playbook::Props::Enum, values: %w[rails react], default: "rails"
       prop :dark, type: Playbook::Props::Boolean, default: false
 
       include PlaybookWebsite::Markdown::Helper
@@ -18,9 +18,6 @@ module Playbook
           render inline: source
         elsif type == "react"
           react_component example_key.camelize, { dark: dark }
-        elsif type == "swift"
-          ## render the markdown file
-          render inline: source
         end
       end
 
@@ -34,11 +31,7 @@ module Playbook
 
       def source
         @source ||= begin
-          extension = if type == "rails"
-                        "html.erb"
-                      else
-                        type == "swift" ? "swift" : "jsx"
-                      end
+          extension = type == "react" ? "jsx" : "html.erb"
           stringified_code = read_kit_file("docs", "_#{example_key}.#{extension}")
           sanitize_code(stringified_code)
         end

data/dist/menu.yml

@@ -90,7 +90,6 @@ kits:
   - typography:
     - body
     - caption
-    - detail
     - title
   - typography_patterns:
     - contact

data/dist/pb_doc_helper.rb

@@ -84,11 +84,8 @@ module PlaybookWebsite
     def pb_doc_render_clickable_title(kit, type)
       url = "#"
       begin
-        url = case type
-              when "react"
+        url = if type == "react"
                 kit_show_reacts_path(kit)
-              when "swift"
-                kit_show_swift_path(kit)
               else
                 kit_show_path(kit)
               end