Skip to content

DEV: Replace <Input /> text usage in plugins #34352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 20, 2025

Conversation

martin-brennan
Copy link
Contributor

Replaces usage of the Ember <Input /> component with
native <input> elements in core plugins for text and
number inputs.

Generated with claude.

Replaces usage of the Ember `<Input />` component with
native `<input>` elements in core plugins for text and
number inputs.

Generated with claude.
@martin-brennan martin-brennan marked this pull request as ready for review August 18, 2025 04:10
@martin-brennan martin-brennan requested a review from CvX August 18, 2025 06:34
Copy link
Contributor

@CvX CvX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A general note about transforming those:

Input component is adding (among other things) a .ember-text-field class to these inputs. I see we use that class in css in core and in custom plugins. Those styles will need to be updated to e.g. also include [type="text"], [type="number"], etc. (when needed)

(not sure if any of those affect inputs modified in this PR)

@martin-brennan martin-brennan requested a review from CvX August 19, 2025 02:55
@martin-brennan martin-brennan merged commit 30e0058 into main Aug 20, 2025
16 checks passed
@martin-brennan martin-brennan deleted the dev/replace-input-usage-plugins branch August 20, 2025 01:23
yuriyaran pushed a commit that referenced this pull request Aug 21, 2025
Replaces usage of the Ember `<Input />` component with
native `<input>` elements in core plugins for text and
number inputs.

Generated with claude.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants