Skip to content

Commit 556fb59

Browse files
committed
Merge branch 'main' into jsys/upgrade-pager-view
2 parents 50d128f + 703cdf4 commit 556fb59

File tree

299 files changed

+6248
-3787
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

299 files changed

+6248
-3787
lines changed

android/app/build.gradle

+2-2
Original file line numberDiff line numberDiff line change
@@ -114,8 +114,8 @@ android {
114114
minSdkVersion rootProject.ext.minSdkVersion
115115
targetSdkVersion rootProject.ext.targetSdkVersion
116116
multiDexEnabled rootProject.ext.multiDexEnabled
117-
versionCode 1009011205
118-
versionName "9.1.12-5"
117+
versionCode 1009011305
118+
versionName "9.1.13-5"
119119
// Supported language variants must be declared here to avoid from being removed during the compilation.
120120
// This also helps us to not include unnecessary language variants in the APK.
121121
resConfigs "en", "es"

android/app/src/main/java/com/expensify/chat/navbar/NavBarManagerModule.kt

+17-1
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
package com.expensify.chat.navbar
22

3+
import android.content.res.Resources
34
import androidx.core.view.WindowInsetsControllerCompat
5+
import com.expensify.chat.R
46
import com.facebook.react.bridge.ReactApplicationContext
57
import com.facebook.react.bridge.ReactContextBaseJavaModule
68
import com.facebook.react.bridge.ReactMethod
7-
import com.facebook.react.bridge.UiThreadUtil;
9+
import com.facebook.react.bridge.UiThreadUtil
810

911
class NavBarManagerModule(
1012
private val mReactContext: ReactApplicationContext,
@@ -24,4 +26,18 @@ class NavBarManagerModule(
2426
}
2527
}
2628
}
29+
30+
@ReactMethod
31+
fun getType(): String {
32+
val resources = mReactContext.resources
33+
val resourceId = resources.getIdentifier("config_navBarInteractionMode", "integer", "android");
34+
if (resourceId > 0) {
35+
val navBarInteractionMode = resources.getInteger(resourceId)
36+
when (navBarInteractionMode) {
37+
0, 1 -> return "soft-keys"
38+
2 -> return "gesture-bar"
39+
}
40+
}
41+
return "soft-keys";
42+
}
2743
}

assets/images/product-illustrations/emptystate__receiptfairy.svg

+154
Loading

contributingGuides/FORMS.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Browsers use the name prop to autofill information into the input. Here's a [ref
6868

6969
```jsx
7070
<InputWrapper
71-
InputComponent={TextInput}
71+
InputComponent={TextInput}
7272
name="fname"
7373
/>
7474
```
@@ -118,7 +118,7 @@ Once a user has “touched” an input, i.e. blurred the input, we will also sta
118118

119119
All form fields will additionally be validated when the form is submitted. Although we are validating on blur this additional step is necessary to cover edge cases where forms are auto-filled or when a form is submitted by pressing enter (i.e. there will be only a ‘submit’ event and no ‘blur’ event to hook into).
120120

121-
The Form component takes care of validation internally and the only requirement is that we pass a validate callback prop. The validate callback takes in the input values as argument and should return an object with shape `{[inputID]: errorMessage}`.
121+
The Form component takes care of validation internally and the only requirement is that we pass a validate callback prop. The validate callback takes in the input values as argument and should return an object with shape `{[inputID]: errorMessage}`.
122122

123123
Here's an example for a form that has two inputs, `routingNumber` and `accountNumber`:
124124

@@ -332,10 +332,10 @@ An example of this can be seen in the [ACHContractStep](https://github.com/Expen
332332
### Safe Area Padding
333333

334334
Any `FormProvider.tsx` that has a button at the bottom. If the `<FormProvider>` is inside a `<ScreenWrapper>`, the bottom safe area inset is handled automatically (`includeSafeAreaPaddingBottom` needs to be set to `true`, but its the default).
335-
If you have custom requirements and can't use `<ScreenWrapper includeSafeAreaPaddingBottom={true}>`, you can use the `useStyledSafeAreaInsets()` hook:
335+
If you have custom requirements and can't use `<ScreenWrapper includeSafeAreaPaddingBottom={true}>`, you can use the `useSafeAreaPaddings()` hook:
336336

337337
```jsx
338-
const { paddingTop, paddingBottom, safeAreaPaddingBottomStyle } = useStyledSafeAreaInsets();
338+
const { paddingTop, paddingBottom, safeAreaPaddingBottomStyle } = useSafeAreaPaddings();
339339

340340
<View styles={[safeAreaPaddingBottomStyle, styles.pb5]}>
341341
<FormProvider>

docs/articles/expensify-classic/bank-accounts-and-payments/Third-Party-Payments.md

-29
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,28 @@
11
---
2-
title: Enable Australian reimbursements
3-
description: Reimburse AUD expenses using ABA files
2+
title: Enable Australian Reimbursements
3+
description: Learn how to reimburse AUD expenses using ABA files in Expensify.
4+
keywords: [Expensify Classic, AUD, reimbursement, ABA file, indirect reimbursement, Expensify, Australian payments]
45
---
56
<div id="expensify-classic" markdown="1">
7+
8+
You can reimburse AUD expenses using **indirect reimbursements**. This allows Australian employees to submit their bank account details in Expensify, which are then provided to you for payment via `.aba` file. A **Workspace Admin** can upload the `.aba` file to the bank to process payments.
69

7-
{% include info.html %}
8-
AUD bank accounts do not rely on direct deposit or ACH.
10+
**Note:** AUD bank accounts do not use direct deposit or ACH.
911

10-
For businesses that will also be reimbursing employees in other countries outside of Australia, you’ll need to set up Global Reimbursement instead.
11-
{% include end-info.html %}
12+
If you'd like an option for direct international payments, consider setting up [global reimbursements](https://help.expensify.com/articles/expensify-classic/bank-accounts-and-payments/bank-accounts/Enable-Global-Reimbursements) instead.
1213

13-
You can reimburse AUD expenses using indirect reimbursements. This allows your Australian employees to submit their personal bank account information to Expensify where it will be provided to you for payment via an .aba file. A Workspace Admin can then upload the .aba file to the bank to have payments issued.
14+
---
1415

15-
To enable ABA payments,
16+
# Setting Up ABA Payments
1617

17-
1. Hover over **Settings**, then click **Workspaces**.
18-
2. Select the desired workspace.
19-
3. Click the **Reports** tab on the left.
20-
4. Click the Report Currency dropdown and select **AUD A$**.
21-
5. Click the **Reimbursement** tab on the left.
22-
6. Select **Indirect** as the Reimbursement type.
18+
1. Go to **Settings > Workspaces**.
19+
2. Select the workspace you want to configure.
20+
3. Click the **Reports** tab.
21+
4. In the **Report Currency** dropdown, select **AUD A$**.
22+
5. Click the **Reimbursement** tab.
23+
6. Set **Reimbursement Type** to **Indirect**.
2324
7. Enable the toggle.
2425

26+
Once enabled, employees can submit expenses in AUD, and you can process reimbursements via ABA files.
27+
2528
</div>

0 commit comments

Comments
 (0)