Skip to content

feat(filter-input): new component#131

Merged
agliga merged 2 commits intomainfrom
filter-input
May 20, 2025
Merged

feat(filter-input): new component#131
agliga merged 2 commits intomainfrom
filter-input

Conversation

@agliga
Copy link
Copy Markdown
Collaborator

@agliga agliga commented May 19, 2025

Fixes #76

  • This PR contains CSS changes
  • This PR does not contain CSS changes

Description

  • Coreui version of component

Screenshots

Screenshot 2025-05-19 at 9 55 10 AM

Checklist

  • I verify the build is in a non-broken state
  • I verify all changes are within scope of the linked issue

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented May 19, 2025

🦋 Changeset detected

Latest commit: 49eade9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@ebay/ebayui-core Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

on-change("emit", "change")
on-input-change("emit", "input")
on-focus("emit", "focus")
on-blur("emit", "blur")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should we pass type="search" by default?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yes will update

inputClass]>
<ebay-textbox
fluid

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

do we need this extra line?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I ran prettier on these. Let me rerun

import { validSizes } from "./constants";


interface FilterInputInput extends Omit<TextboxInput, `on${string}`> {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It seems we are not passing some non HTML attributes, like floating-label for example. Are we supposed to support those here also? If that is not the case we need to omit those from the input type also.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

We can but it starts to become a managing nightmare if we add more things to textbox.
This is true for number input as well.
I think the documentation in storybook should be our source of truth.
If someone uses an attribute and its not supported and not in storybook then that's on them.

@agliga agliga merged commit 4f38946 into main May 20, 2025
3 checks passed
@agliga agliga deleted the filter-input branch May 20, 2025 18:40
@github-actions github-actions bot mentioned this pull request May 20, 2025
This was referenced May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

search-text: marko component

2 participants