discourse/app/assets/stylesheets/common/form-kit/_control-menu.scss

.form-kit__control-menu-trigger {
  @include default-input;
  justify-content: space-between;
}

.form-kit__control-menu-content {
  .dropdown-menu {
    min-width: 200px;
  }

  .dropdown-menu__item {
    &:hover {
      background: var(--d-hover);
    }
  }
}
DEV: unifies emoji picker (#28277) The chat emoji picker is renamed emoji-picker, and the old emoji-picker is removed. This commit doesn't attempt to fully rework a new emoji-picker but instead tries to migrate everything to one picker (the chat one) and add small changes. Other notable changes: - all the favorite emojis code has been mixed into one service which is able to store one state per context, favorites emojis will be stored for all topics, and for each chat channel. Meaning that if you always use a specific emoji in a channel, it will only show as favorite emoji in this channel. - a lot of static code has been removed which should improve initial load perf of discourse. Initially this code was around to improve the performance of the emoji picker rendering. - the emojis are now stored, once the full list has been loaded, if you close and reopen the picker it won't have to load them again. List of components: - `<EmojiPicker />` will render a button which will open a dropdown - `<EmojiPickerContent />` represents the content of the dropdown alone, it's useful when you want to render a picker from an action which is not the default picker button - `<EmojiPickerDetached />` just a simple wrapper over `<EmojiPickerContent />` to make it easier to use it with `this.menu.show(...)` --------- Co-authored-by: Renato Atilio <renatoat@gmail.com> 2025-01-08 11:41:36 +01:00			`.form-kit__control-menu-trigger {`
DEV: form-kit This PR introduces FormKit, a component-based form library designed to simplify form creation and management. This library provides a single `Form` component, various field components, controls, validation mechanisms, and customization options. Additionally, it includes helpers to facilitate testing and writing specifications for forms. 1. Form Component: - The main component that encapsulates form logic and structure. - Yields various utilities like `Field`, `Submit`, `Alert`, etc. Example Usage: ```gjs import Form from "discourse/form"; <template> <Form as \|form\|> <form.Field @name="username" @title="Username" @validation="required" as \|field\| > <field.Input /> </form.Field> <form.Field @name="age" @title="Age" as \|field\|> <field.Input @type="number" /> </form.Field> <form.Submit /> </Form> </template> ``` 2. Validation: - Built-in validation rules such as `required`, `number`, `length`, and `url`. - Custom validation callbacks for more complex validation logic. Example Usage: ```javascript validateUsername(name, value, data, { addError }) { if (data.bar / 2 === value) { addError(name, "That's not how maths work."); } } ``` ```hbs <form.Field @name="username" @validate={{this.validateUsername}} /> ``` 3. Customization: - Plugin outlets for extending form functionality. - Styling capabilities through propagated attributes. - Custom controls with properties provided by `form` and `field`. Example Usage: ```hbs <Form class="my-form" as \|form\|> <form.Field class="my-field" as \|field\|> <MyCustomControl id={{field.id}} @onChange={{field.set}} /> </form.Field> </Form> ``` 4. Helpers for Testing: - Test assertions for form and field validation. Example usage: ```javascript assert.form().hasErrors("the form shows errors"); assert.form().field("foo").hasValue("bar", "user has set the value"); ``` - Helper for interacting with he form Example usage: ```javascript await formKit().field("foo").fillIn("bar"); ``` 5. Page Object for System Specs: - Page objects for interacting with forms in system specs. - Methods for submitting forms, checking alerts, and interacting with fields. Example Usage: ```ruby form = PageObjects::Components::FormKit.new(".my-form") form.submit expect(form).to have_an_alert("message") ``` Field Interactions: ```ruby field = form.field("foo") expect(field).to have_value("bar") field.fill_in("bar") ``` 6. Collections handling: - A specific component to handle array of objects Example Usage: ```gjs <Form @data={{hash foo=(array (hash bar=1) (hash bar=2))}} as \|form\|> <form.Collection @name="foo" as \|collection\|> <collection.Field @name="bar" @title="Bar" as \|field\|> <field.Input /> </collection.Field> </form.Collection> </Form> ``` 2024-07-17 11:59:35 +02:00			`@include default-input;`
DEV: Convert group SMTP settings form to FormKit (#27965) This commit changes the group SMTP settings form (at `/g/:name/manage/email`) to use FormKit, our magical new form component system :sparkles: --------- Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com> 2024-07-24 09:52:52 +10:00			`justify-content: space-between;`
DEV: form-kit This PR introduces FormKit, a component-based form library designed to simplify form creation and management. This library provides a single `Form` component, various field components, controls, validation mechanisms, and customization options. Additionally, it includes helpers to facilitate testing and writing specifications for forms. 1. Form Component: - The main component that encapsulates form logic and structure. - Yields various utilities like `Field`, `Submit`, `Alert`, etc. Example Usage: ```gjs import Form from "discourse/form"; <template> <Form as \|form\|> <form.Field @name="username" @title="Username" @validation="required" as \|field\| > <field.Input /> </form.Field> <form.Field @name="age" @title="Age" as \|field\|> <field.Input @type="number" /> </form.Field> <form.Submit /> </Form> </template> ``` 2. Validation: - Built-in validation rules such as `required`, `number`, `length`, and `url`. - Custom validation callbacks for more complex validation logic. Example Usage: ```javascript validateUsername(name, value, data, { addError }) { if (data.bar / 2 === value) { addError(name, "That's not how maths work."); } } ``` ```hbs <form.Field @name="username" @validate={{this.validateUsername}} /> ``` 3. Customization: - Plugin outlets for extending form functionality. - Styling capabilities through propagated attributes. - Custom controls with properties provided by `form` and `field`. Example Usage: ```hbs <Form class="my-form" as \|form\|> <form.Field class="my-field" as \|field\|> <MyCustomControl id={{field.id}} @onChange={{field.set}} /> </form.Field> </Form> ``` 4. Helpers for Testing: - Test assertions for form and field validation. Example usage: ```javascript assert.form().hasErrors("the form shows errors"); assert.form().field("foo").hasValue("bar", "user has set the value"); ``` - Helper for interacting with he form Example usage: ```javascript await formKit().field("foo").fillIn("bar"); ``` 5. Page Object for System Specs: - Page objects for interacting with forms in system specs. - Methods for submitting forms, checking alerts, and interacting with fields. Example Usage: ```ruby form = PageObjects::Components::FormKit.new(".my-form") form.submit expect(form).to have_an_alert("message") ``` Field Interactions: ```ruby field = form.field("foo") expect(field).to have_value("bar") field.fill_in("bar") ``` 6. Collections handling: - A specific component to handle array of objects Example Usage: ```gjs <Form @data={{hash foo=(array (hash bar=1) (hash bar=2))}} as \|form\|> <form.Collection @name="foo" as \|collection\|> <collection.Field @name="bar" @title="Bar" as \|field\|> <field.Input /> </collection.Field> </form.Collection> </Form> ``` 2024-07-17 11:59:35 +02:00			`}`
DEV: unifies emoji picker (#28277) The chat emoji picker is renamed emoji-picker, and the old emoji-picker is removed. This commit doesn't attempt to fully rework a new emoji-picker but instead tries to migrate everything to one picker (the chat one) and add small changes. Other notable changes: - all the favorite emojis code has been mixed into one service which is able to store one state per context, favorites emojis will be stored for all topics, and for each chat channel. Meaning that if you always use a specific emoji in a channel, it will only show as favorite emoji in this channel. - a lot of static code has been removed which should improve initial load perf of discourse. Initially this code was around to improve the performance of the emoji picker rendering. - the emojis are now stored, once the full list has been loaded, if you close and reopen the picker it won't have to load them again. List of components: - `<EmojiPicker />` will render a button which will open a dropdown - `<EmojiPickerContent />` represents the content of the dropdown alone, it's useful when you want to render a picker from an action which is not the default picker button - `<EmojiPickerDetached />` just a simple wrapper over `<EmojiPickerContent />` to make it easier to use it with `this.menu.show(...)` --------- Co-authored-by: Renato Atilio <renatoat@gmail.com> 2025-01-08 11:41:36 +01:00
			`.form-kit__control-menu-content {`
			`.dropdown-menu {`
			`min-width: 200px;`
			`}`
DEV: Introduce stylelint (#29852) Stylelint is a css linter: https://stylelint.io/ As part of this change we have added two javascript scripts: ``` pnpm lint:css pnpm lint:css:fix ``` Look at `.vscode/settings.json.sample` and `.vscode/extensions.json` for configuration in VSCode. --------- Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com> 2025-01-20 15:27:42 +00:00
DEV: unifies emoji picker (#28277) The chat emoji picker is renamed emoji-picker, and the old emoji-picker is removed. This commit doesn't attempt to fully rework a new emoji-picker but instead tries to migrate everything to one picker (the chat one) and add small changes. Other notable changes: - all the favorite emojis code has been mixed into one service which is able to store one state per context, favorites emojis will be stored for all topics, and for each chat channel. Meaning that if you always use a specific emoji in a channel, it will only show as favorite emoji in this channel. - a lot of static code has been removed which should improve initial load perf of discourse. Initially this code was around to improve the performance of the emoji picker rendering. - the emojis are now stored, once the full list has been loaded, if you close and reopen the picker it won't have to load them again. List of components: - `<EmojiPicker />` will render a button which will open a dropdown - `<EmojiPickerContent />` represents the content of the dropdown alone, it's useful when you want to render a picker from an action which is not the default picker button - `<EmojiPickerDetached />` just a simple wrapper over `<EmojiPickerContent />` to make it easier to use it with `this.menu.show(...)` --------- Co-authored-by: Renato Atilio <renatoat@gmail.com> 2025-01-08 11:41:36 +01:00			`.dropdown-menu__item {`
			`&:hover {`
			`background: var(--d-hover);`
			`}`
			`}`
			`}`