Skip to content
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

feat: input component #129

Merged
merged 41 commits into from
Jul 1, 2022
Merged

feat: input component #129

merged 41 commits into from
Jul 1, 2022

Conversation

muratcorlu
Copy link
Contributor

@muratcorlu muratcorlu commented Jun 21, 2022

Known issues:

  • Storybook demos for validation and focus states don't have a proper visual regression tests
  • Component argument reference has duplicate values for the properties like help-text since its property is helpText. We need to analyze how to properly document properties and attributes.

Also there are many missing features that we'll need near future for sure. But we wanted to iterate on this because input component is a quite complex component and we thought it makes sense to improve it step by step.

@muratcorlu muratcorlu linked an issue Jun 21, 2022 that may be closed by this pull request
@muratcorlu
Copy link
Contributor Author

Medium input height looks 32.5px, should be 32px. Also, Large input height looks 40.5px, should be 40px.

We were using line-height for calculating input height but while we are implementing bl-badge (#131) we converted values to rem and decided to starting setting height. Once that PR merged, we needed to update current components (including button @leventozen ) to use this new approach.

I fixed it and should be ok now.

@leventozen
Copy link
Member

leventozen commented Jun 30, 2022

Medium input height looks 32.5px, should be 32px. Also, Large input height looks 40.5px, should be 40px.

We were using line-height for calculating input height but while we are implementing bl-badge (#131) we converted values to rem and decided to starting setting height. Once that PR merged, we needed to update current components (including button @leventozen ) to use this new approach.

I fixed it and should be ok now.

Yes, I am aware of it. I commented for this reason. I checked, seems done 👍

@buseselvi
Copy link
Contributor

buseselvi commented Jun 30, 2022

When error message appears in the input validation section in storybook, the other input slides down, can we fix it so that it stays above? When we show descriptions, the alignment of the other inputs should not change.

Ekran Resmi 2022-06-30 17 52 26

@muratcorlu
Copy link
Contributor Author

When error message appears in the input validation section in storybook, the other input slides down, can we fix it so that it stays above? When we show descriptions, the alignment of the other inputs should not change.

Ekran Resmi 2022-06-30 17 52 26

This is fixed.

image

But for doing that, I just styled demo pane to align component demostrations to the top. As a result of this that demo looks not aligned but I think we'll accept that. Right?

image

@buseselvi
Copy link
Contributor

If we can't do bottom alignment in this part separately, can we put these 3 input types one under the other? We do not use inputs in different label styles side by side in the design.

Also, the text color of the input on the right looks different from the others, can we check?

@muratcorlu
Copy link
Contributor Author

@buseselvi Good catch! 😊 Fixed it. Please check this version. Storybook will be re-rendered soon.

image

src/themes/default.css Outdated Show resolved Hide resolved
@muratcorlu muratcorlu requested review from DamlaDemir and removed request for leventozen July 1, 2022 12:26
@buseselvi
Copy link
Contributor

Can we make the label background primary background color (white)?

image

@leventozen leventozen added this to the v2.0 milestone Jul 1, 2022
@muratcorlu muratcorlu merged commit 66ec832 into next Jul 1, 2022
@muratcorlu muratcorlu deleted the 87-input-component branch July 1, 2022 13:30
@github-actions
Copy link

github-actions bot commented Jul 1, 2022

🎉 This PR is included in version 2.0.0-beta.11 🎉

The release is available on:

Your semantic-release bot 📦🚀

mehmetranas pushed a commit that referenced this pull request Jul 19, 2022
* feat: input component first boilerplate

* feat: input work in progress

* feat(input): more attributes are defined

* feat(input): set validity with custom validation

* feat(input): styling input

* feat: input error validation and label defined

* feat(input): added input medium features

* feat(input): added input large, added all types

* test(input): some tests are added

* test: fix esbuild plugin causes ts decorators dont run

* test(input): test coverage increased

* refactor(input): linter fixes

* docs(input): story file created

* docs(storybook): adding user interaction test addon

* feat: adding reportValidity method

* docs(storybook): adding basic input ant input labels

* refactor: linter fixes

* fix(input): label-fixed placeholder visibility

* test: include styles in unit tests (#133)

Co-authored-by: Murat Çorlu <murat.corlu@trendyol.com>

* test: clean forgotten tag in test html

* test: dependency fix

* refactor: linter fix

* refactor: linter fix

* fix(storybook): version fixed to 6.5.5

* docs(input): storybook doc improved

* fix(input): css lint fix

* fix(input): css part definition forgotten in the code

* fix(input): font style fixed

* fix(input): ui fixes with new rem sizes

* chore(storybook): multi column demos aligned top

* refactor(input): private properties pointed, better jsdoc

* refactor: better web component analyzer

* fix(input): placeholder color fix

* fix(design): duplicate colors removed

* fix(input): label bg color fixed

Co-authored-by: mehmet.tanas <mehmet.tanas@trendyol.com>
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

Input Component
4 participants