-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-10-02] [HOLD for payment 2023-09-07] [HOLD for payment 2023-09-04] [HOLD for payment 2023-08-24] [HOLD for payment 2023-08-17] [HOLD for payment 2023-08-10] [HOLD for payment 2023-08-08] [HOLD for payment 2023-08-07] [HOLD for payment 2023-08-03] [HOLD for payment 2023-08-02] [HOLD for payment 2023-08-01] [HOLD for payment 2023-07-28] [HOLD for payment 2023-07-26] [HOLD for payment 2023-07-24] [HOLD for payment 2023-07-21] [HOLD for payment 2023-07-20] [HOLD for payment 2023-07-17] [HOLD for payment 2023-07-14] Implement custom buttons #123
Comments
Actually... seems like we're good if we use the |
I agree this is valuable, but demoting to MEDIUM because it's only experienced once per session and will be instantly forgotten. yes those who study the code will have this question, but let's focus first on a flawless live demo. |
Yeah, TouchableOpacity seems to work fine for this. When we actually build this out in the future, we'd want to make our own custom button component where we can pass through things like |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @Santhosh-Sellavel ( |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak ( |
Job added to Upwork: https://www.upwork.com/jobs/~01e492b331c8133b5b |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @thesahindia ( |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.37-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-07-14. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Triggered auto assignment to @Gonals, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.57-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-09-04. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.60-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-09-07. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.73-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-02. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
hahaha.... oops. I guess using |
Unfortunately we can't really add any styles to the out-of-the-box RN buttons:
However, it seems like there are a lot of ready-to-use solutions out there using the
TouchableXXXX
components.Here is a good example from Facebook: https://github.com/facebook/react-native/blob/master/Libraries/Components/Button.js
More reading: https://stackoverflow.com/questions/43585297/react-native-button-style-not-work
I think this is high priority because it will help prove that we have full style control over simple form elements.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: