@primer/view-components 0.37.0-rc.c14337fb → 0.37.0-rc.e9e06c44

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@primer/view-components",
-  "version": "0.37.0-rc.c14337fb",
+  "version": "0.37.0-rc.e9e06c44",
   "description": "ViewComponents for the Primer Design System",
   "main": "app/assets/javascripts/primer_view_components.js",
   "module": "app/components/primer/primer.js",

package/static/info_arch.json

@@ -2838,7 +2838,7 @@
     "description": "Check boxes are true/false inputs rendered as `<input type=\"checkbox\">` in HTML.\n\n## Schemes\n\nCheck boxes can submit values to the server using one of two schemes, either `:array`\nor `:boolean` (the default). Check boxes with a scheme of `:boolean` function like normal\nHTML check boxes. If they are checked, a value of \"1\" is sent to the server; if they are\nunchecked, a value of \"0\" is sent to the server. The checked and unchecked values can be\ncustomized via the `:value` and `:unchecked_value` arguments respectively.\n\nWhereas `:boolean` check boxes must have unique names, `:array` check boxes all have the\nsame name. On form submission, Rails will aggregate the values of the check boxes with the\nsame name and provide them to the controller as an array. If `:scheme:` is `:array`, the\n`:value` argument must also be provided. The `:unchecked_value` argument is ignored. If a\ncheck box is checked on submit, its corresponding value will appear in the array. If it is\nnot checked, its value will not appear in the array.\n\n## Caption templates\n\nCaption templates for `:array`-type check boxes work a little differently than they do for\nother input types. Because the name must be the same for all check boxes that make up an\narray, caption template file names are comprised of both the name _and_ the value of each\ncheck box. For example, a check box with the name `foo` and value `bar` must have a caption\ntemplate named `foo_bar_caption.html.erb`.\n\n## Nested Forms\n\nCheck boxes can have \"nested\" forms that are rendered below the caption. A common use-case\nis a form that is hidden until the check box is checked. Nested forms are indented slightly\nto align with the label and caption.\n\nDefine a nested form via the `#nested_form` method, which is expected to return an instance\nof a Primer form (see the usage section below).\n\nAny fields defined in the nested form are submitted along with the parent form's fields.\n\n**NOTE**: Check boxes do not automatically show or hide nested forms. If such behavior is\ndesired, it must be done by hand.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "CheckBox",
     "status": "alpha",
@@ -3075,7 +3075,7 @@
     "description": "Check box groups consist of one or more related check boxes.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "CheckBoxGroup",
     "status": "alpha",
@@ -4206,7 +4206,7 @@
     "description": "A button input rendered using the HTML `<button type=\"button\">` tag.\n\nThis component wraps the Primer button component and supports the same slots and arguments.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "FormButton",
     "status": "alpha",
@@ -4281,7 +4281,7 @@
     "fully_qualified_name": "Primer::Alpha::FormControl",
     "description": "Wraps an input (or arbitrary content) with a label above and a caption and validation message beneath.\n\nNOTE: This `FormControl` component is designed for wrapping inputs that aren't supported by the Primer\nforms framework.",
     "accessibility_docs": "Because `FormControl` does not manage the actual `<input>` element, it cannot semantically connect\nthe input and its associated label. For this and other reasons, consumers are highly encouraged to\nuse Primer's pre-made form components like `TextField`, etc, ideally via the Primer forms framework.\n\nUsers of the `FormControl` component will need to manually connect the label using the `for:`\nattribute, eg:\n\n```erb\n<%= form_with(url: \"/path/somewhere\") do |f| %>\n  <%= render(Primer::Alpha::FormControl.new(label_arguments: { for: \"bar\" })) do |component| %>\n    <% component.with_input do |input_arguments| %>\n      <%= f.text_field(:bar, **input_arguments) %>\n    <% end %>\n  <% end %>\n<% end %>\n```\n\nNote that the name of the field, `:bar`, is passed to both the Rails `#text_field` method _and_\nas part of the `label_arguments` passed to the `FormControl` constructor.\n\nSimilarly, `FormControl` cannot automatically connect the `<input>` element to the caption and\nvalidation message elements. The component attempts to mitigate this by including the correct\n`aria-describedby` attribute in the hash it yields to the block passed to `#with_input`. In the\nexample above, `input_arguments[:aria][:describedby]` contains the HTML IDs for both the caption\nand validation message elements, and can be passed directly to Rails' form helper methods. If the\ninput being wrapped is not generated by a Rails form helper, care must be taken to set\n`aria-describedby` manually on the input element.",
-    "is_form_component": true,
+    "is_form_component": false,
     "is_published": true,
     "requires_js": false,
     "component": "FormControl",
@@ -5210,7 +5210,7 @@
     "description": "Multi inputs are comprised of multiple constituent fields, only one of which is visible\nat a given time. They are designed for situations where constituent inputs are shown or\nhidden based on the value of another field. For example, consider an address form. If\nthe user chooses the USA as the country, the region input should show a list of states\nand US territories; if the user instead chooses Canada, the region input should show a\nlist of Canadian provinces, etc.\n\nUnlike everywhere else in Primer forms, constituent inputs are not directly passed a\n`name` attribute. Instead, developers pass a `name` attribute to the multi input itself.\nThe multi input then automatically assigns each constituent input the same name. This is\ndone so that the multi input looks like a single field from the server's point of view.\nUsing the address form example from earlier, this means only one value - either a US state\nor a Canadian provice - will be submitted to the server under the `region` key.\n\nActually, that's not quite true. Constituent inputs _are_ given a `name`, but it's added to\nthe input as the `data-name` attribute as a way to identify constituent inputs, and will not\nbe sent to the server.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": true,
     "component": "MultiInput",
     "status": "alpha",
@@ -6419,7 +6419,7 @@
     "description": "Radio buttons represent one of a set of options and are rendered as `<input type=\"radio\">` in HTML.\n**NOTE**: You probably want to use the {{#link_to_component}}Primer::Alpha::RadioButtonGroup{{/link_to_component}}\ncomponent instead, as it allows rendering a group of options.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "RadioButton",
     "status": "alpha",
@@ -6632,7 +6632,7 @@
     "description": "A group of mutually exclusive radio buttons.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "RadioButtonGroup",
     "status": "alpha",
@@ -7145,7 +7145,7 @@
     "description": "Select lists are single-line text inputs rendered as `<select>` tags in HTML.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "Select",
     "status": "alpha",
@@ -8343,7 +8343,7 @@
     "description": "A submit button input rendered using the HTML `<button type=\"submit\">` tag.\n\nThis component wraps the Primer button component and supports the same slots and arguments.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "SubmitButton",
     "status": "alpha",
@@ -8716,7 +8716,7 @@
     "description": "Text areas are multi-line text inputs rendered using the `<textarea>` tag in HTML.",
     "accessibility_docs": null,
     "is_form_component": true,
-    "is_published": true,
+    "is_published": false,
     "requires_js": false,
     "component": "TextArea",
     "status": "alpha",
@@ -8975,7 +8975,7 @@
     "accessibility_docs": null,
     "is_form_component": true,
     "is_published": true,
-    "requires_js": true,
+    "requires_js": false,
     "component": "TextField",
     "status": "alpha",
     "a11y_reviewed": false,