fix(text-field)!: rename props existing in native input to avoid conflict with lp #446
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
paulosoaresvieira
approved these changes
May 10, 2024
djcouto
force-pushed
the
dc/input-disabled
branch
2 times, most recently
from
f95d9ba
to
225525b
Compare
djcouto
changed the title
input to input-disabled to avoid conflict with lp
…lict with lp BREAKING-CHANGE: - `disabled` was renamed to `input-disabled` - `readonly` was renamed to `input-readonly` - `required` was renamed to `input-required`
djcouto
force-pushed
the
dc/input-disabled
branch
from
225525b
to
49bce1c
Compare
GoncaloCamaz
approved these changes
May 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING-CHANGE:
-
disabledwas renamed toinput-disabled-
readonlywas renamed toinput-readonly-
requiredwas renamed toinput-required