-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Switched the CheckboxInput component to use Checkbox.Item to stay mor… #56
Switched the CheckboxInput component to use Checkbox.Item to stay mor… #56
Conversation
…e consistent with RN paper and allow for the mode parameter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
React native paper uses checkboxes after the line of text, that doesn't look good in the select.
I would not accept the PR in the current state without providing an alternative to still have the text default to being right aligned.
@Thodor12 Please note in this PR I have set the 'position' property to 'leading'. This puts the checkbox on the left side of the text. The implementation is the same as before. It just stays more consistent with React Native Paper's styling. It also adds the mode property. Thanks for the review. |
… for RNP Theme Provider to take full control.
Now also includes bug fixes for #53 and #49 as per @srivastavaanurag79 request. @CarlosSLoureiro or @Thodor12 could you please review? |
With all the individual property additions, isn't it easier to just inherit the typings from the paper checkbox and using rest parameters to pass everything at once to the checkbox? (Whilst making sure to omit certain things we have to explicitly set) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could I also get a before and after of how it looks, with pure basic configuration, no modified theming, etc.
If the UI changes it might have to be marked as a breaking change.
@Thodor12 UI changes are minimal. Seems like you are grilling me for no reason on this PR. It’s pretty straightforward. |
@himrocks33 Please add this feature to this merge request,i.e, limiter, a key name **Future Features #59 **:
|
If you think that that is your problem. All I'm asking for is a simple before and after. I see a bunch of changes and I've got no idea of the impact of this. |
It will be a breaking change since the checkbox style is being changed and some other new features are being added as well. The pull request will be strictly reviewed so please be patient and please be a bit polite everyone. |
@Thodor12 If you have time please switch to @himrocks33 branch and run the project to review the changes and update it with your guidance if you find something unusual or not needed. |
I got pretty busy at work again for the time being. I feel like there is enough here for a feature release though. @srivastavaanurag79 |
@srivastavaanurag79 #59 items seem like a complete rewrite almost to support the single select (which would probably be a whole new component really?) I doubt I have time for that right now. Bug Fixes and minor changes I can do. Where do we stand with getting this PR merged? |
@himrocks33 #59 you Don't have to do them, those are future features |
@himrocks33 if adding a limiter feature is possible please add it, a key name limit which limits the maximum number of items one can select in the multi-select, will try to review and merge this pull request this Sunday by myself if other contributors don't have time for the same. |
feat: limit?: number | null; limitError?: string; limitErrorStyle?: TextStyle; limit the number of items one can select in multi select.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed all the changes. The major change was in the checkbox. Touchable Opacity was removed but it would not break any existing installed version. The code looks fine. I addressed the issues which I found.
Switched the CheckboxInput component to use Checkbox.Item to stay more consistent with RN paper and allow for the mode parameter.
This will use Text from RN Paper for the label as well keeping the theme consistent.