playbook_ui 13.9.0 → 13.10.0.pre.alpha.PLAY978alphatesthighcharts41330

data/lib/playbook/version.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
 module Playbook
-  PREVIOUS_VERSION = "13.8.0"
-  VERSION = "13.9.0"
+  PREVIOUS_VERSION = "13.10.0"
+  VERSION = "13.10.0.pre.alpha.PLAY978alphatesthighcharts41330"
 end

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: playbook_ui
 version: !ruby/object:Gem::Version
-  version: 13.9.0
+  version: 13.10.0.pre.alpha.PLAY978alphatesthighcharts41330
 platform: ruby
 authors:
 - Power UX
 - Power Devs
-autorequire:
+autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-10-05 00:00:00.000000000 Z
+date: 2023-10-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: actionpack
@@ -276,16 +276,18 @@ files:
 - app/pb_kits/playbook/pb_avatar/avatar.test.js
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_default.html.erb
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_default.jsx
+- app/pb_kits/playbook/pb_avatar/docs/_avatar_default_swift.md
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_monogram.html.erb
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_monogram.jsx
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_monogram.md
+- app/pb_kits/playbook/pb_avatar/docs/_avatar_monogram_swift.md
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_no_image.html.erb
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_no_image.jsx
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_no_image.md
+- app/pb_kits/playbook/pb_avatar/docs/_avatar_props_swift.md
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_status.html.erb
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_status.jsx
 - app/pb_kits/playbook/pb_avatar/docs/_avatar_status.md
-- app/pb_kits/playbook/pb_avatar/docs/_avatar_swift.md
 - app/pb_kits/playbook/pb_avatar/docs/_description.md
 - app/pb_kits/playbook/pb_avatar/docs/_footer.md
 - app/pb_kits/playbook/pb_avatar/docs/example.yml
@@ -1498,6 +1500,8 @@ files:
 - app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_selected_ids.html.erb
 - app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_selected_ids.jsx
 - app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_selected_ids.md
+- app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_single.html.erb
+- app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_single.jsx
 - app/pb_kits/playbook/pb_multi_level_select/docs/_multi_level_select_with_form.html.erb
 - app/pb_kits/playbook/pb_multi_level_select/docs/example.yml
 - app/pb_kits/playbook/pb_multi_level_select/docs/index.js
@@ -2639,7 +2643,7 @@ homepage: https://playbook.powerapp.cloud/
 licenses:
 - ISC
 metadata: {}
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -2650,12 +2654,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - ">"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubygems_version: 3.3.7
-signing_key:
+signing_key: 
 specification_version: 4
 summary: Playbook Design System
 test_files: []

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

@@ -1,82 +0,0 @@
-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