-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'Expensify:main' into issue37153
- Loading branch information
Showing
77 changed files
with
681 additions
and
856 deletions.
There are no files selected for viewing
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
13 changes: 13 additions & 0 deletions
13
docs/articles/expensify-classic/expenses/Export-expenses.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| --- | ||
| title: Export expenses | ||
| description: Export expenses to a CSV | ||
| --- | ||
| <div id="expensify-classic" markdown="1"> | ||
|
|
||
| 1. Click the **Expenses** tab. | ||
| 2. Select the expenses you want to export by checking the box to the left of each expense or selecting them all. | ||
| 3. Click **Export To** in the right corner and select either: | ||
| - **Default CSV**: Use Expensify’s default template | ||
| - **Create new CSV export layout**: Create your own custom CSV template | ||
|
|
||
| </div> |
30 changes: 30 additions & 0 deletions
30
...ticles/expensify-classic/workspaces/Assign-billing-owner-and-payment-account.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| --- | ||
| title: Assign billing owner and payment account | ||
| description: Determine who will cover the cost of the workspace and link a payment method | ||
| --- | ||
| <div id="expensify-classic" markdown="1"> | ||
|
|
||
| The person who creates a workspace will automatically be responsible for the billing for that workspace. However, the existing billing owner can transfer the workspace’s billing ownership to any Admin on the workspace. | ||
|
|
||
| {% include info.html %} | ||
| There can only be one billing owner at a time. Assigning a new billing owner will automatically un-assign the existing billing owner. However, billing owners are also workspace admins by default, and the previous billing owner will remain a workspace admin unless manually updated. | ||
| {% include end-info.html %} | ||
|
|
||
| # Assign a new billing owner | ||
|
|
||
| To assign a new billing owner, **the person who will take over responsibility for the workspace billing must complete the following process**: | ||
|
|
||
| 1. Hover over Settings, then click **Workspaces**. | ||
| 2. Click the desired workspace name. | ||
| 3. Under Workspace Overview, click **Take Over Billing**. | ||
|
|
||
| # Add or update payment account | ||
|
|
||
| Once you take over billing for a workspace, you must add a payment method to your account. | ||
|
|
||
| 1. Hover over Settings, then click **Account**. | ||
| 2. Click the **Payments** tab. | ||
| 3. Scroll down to the Payment Details sections and click **Add Payment Card**. | ||
| 4. Enter your credit or debit card information and click **Accept terms, add payment card, and pay $0.00** (the box will only show a balance if one is due). | ||
|
|
||
| </div> |
24 changes: 24 additions & 0 deletions
24
docs/articles/expensify-classic/workspaces/Create-a-group-workspace.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| --- | ||
| title: Create a group workspace | ||
| description: Create a workspace for your team's expense reports | ||
| --- | ||
| <div id="expensify-classic" markdown="1"> | ||
|
|
||
| A workspace is the set of rules, settings, and spending limits for expense reports in your organization. This includes the unique expense categories and tags, budgets, currency and tax settings, etc. that all workspace members will use. A workspace also defines the approval workflow for your employees, as well as the accounting connection if using an accounting software integration. | ||
|
|
||
| Here are a couple examples of when you’d want to create different workspaces: | ||
|
|
||
| - You have employees with expense reports in different currencies. For example, you may have a workspace for employees who live in the US and submit their reports in USD and a workspace for employees who live in Canada and submit in CAD. | ||
| - You want to limit specific groups of people to their own set of expense coding options (categories/tags) then they can separate their employees by Sales, Marketing, Support, etc. | ||
|
|
||
| To create a group workspace, | ||
|
|
||
| 1. Hover over Settings, then click **Workspaces**. | ||
| 2. Click the **Group** tab on the left. | ||
| 3. Click **New Workspace**. | ||
| 4. Enter the workspace name and select a workspace type. | ||
| - **Collect**: Ideal for small groups who only need basic features like expense approvals, reimbursement, corporate card management, and integration options. | ||
| - **Control**: For groups that need a deeper level of control and configurations, like multi-stage approval workflows, corporate card management, integrations, and more. This is the most popular option. | ||
| 5. Set up your workspace details including the workspace name, expense rules, categories, and more. | ||
|
|
||
| </div> |
20 changes: 20 additions & 0 deletions
20
docs/articles/expensify-classic/workspaces/Set-up-your-individual-workspace.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| --- | ||
| title: Set up your individual workspace | ||
| description: Capture your personal expenses | ||
| --- | ||
| <div id="expensify-classic" markdown="1"> | ||
|
|
||
| All Expensify accounts come with an individual workspace where you can track your personal expenses. If you want to connect your personal expenses to an accounting or travel integration, you can create a group workspace—even if you will be the only person in the group. | ||
|
|
||
| To set up your individual workspace, | ||
|
|
||
| 1. Hover over Settings, then click **Workspaces**. | ||
| 2. Click the **Individual** tab on the left. | ||
| 3. Select the policy type that best fits your needs. | ||
| 4. Set up your workspace details including the workspace name, expense rules, categories, and more. | ||
|
|
||
| {% include info.html %} | ||
| You can create multiple group workspaces, but you can only create one individual workspace. | ||
| {% include end-info.html %} | ||
|
|
||
| </div> |
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
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
43 changes: 43 additions & 0 deletions
43
patches/react-native-web+0.19.9+006+fixPointerEventDown.patch
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| diff --git a/node_modules/react-native-web/dist/modules/useResponderEvents/ResponderSystem.js b/node_modules/react-native-web/dist/modules/useResponderEvents/ResponderSystem.js | ||
| index 0aec2d6..a71aec2 100644 | ||
| --- a/node_modules/react-native-web/dist/modules/useResponderEvents/ResponderSystem.js | ||
| +++ b/node_modules/react-native-web/dist/modules/useResponderEvents/ResponderSystem.js | ||
| @@ -133,7 +133,7 @@ to return true:wantsResponderID| | | ||
|
|
||
| import createResponderEvent from './createResponderEvent'; | ||
| import { isCancelish, isEndish, isMoveish, isScroll, isSelectionChange, isStartish } from './ResponderEventTypes'; | ||
| -import { getLowestCommonAncestor, getResponderPaths, hasTargetTouches, hasValidSelection, isPrimaryPointerDown, setResponderId } from './utils'; | ||
| +import { getLowestCommonAncestor, getResponderPaths, hasTargetTouches, hasValidSelection, isPrimaryOrSecondaryPointerDown, setResponderId } from './utils'; | ||
| import { ResponderTouchHistoryStore } from './ResponderTouchHistoryStore'; | ||
| import canUseDOM from '../canUseDom'; | ||
|
|
||
| @@ -225,7 +225,7 @@ function eventListener(domEvent) { | ||
| } | ||
| return; | ||
| } | ||
| - var isStartEvent = isStartish(eventType) && isPrimaryPointerDown(domEvent); | ||
| + var isStartEvent = isStartish(eventType) && isPrimaryOrSecondaryPointerDown(domEvent); | ||
| var isMoveEvent = isMoveish(eventType); | ||
| var isEndEvent = isEndish(eventType); | ||
| var isScrollEvent = isScroll(eventType); | ||
| diff --git a/node_modules/react-native-web/dist/modules/useResponderEvents/utils.js b/node_modules/react-native-web/dist/modules/useResponderEvents/utils.js | ||
| index 7382cdd..d88f6c0 100644 | ||
| --- a/node_modules/react-native-web/dist/modules/useResponderEvents/utils.js | ||
| +++ b/node_modules/react-native-web/dist/modules/useResponderEvents/utils.js | ||
| @@ -148,14 +148,14 @@ export function hasValidSelection(domEvent) { | ||
| /** | ||
| * Events are only valid if the primary button was used without specific modifier keys. | ||
| */ | ||
| -export function isPrimaryPointerDown(domEvent) { | ||
| +export function isPrimaryOrSecondaryPointerDown(domEvent) { | ||
| var altKey = domEvent.altKey, | ||
| button = domEvent.button, | ||
| buttons = domEvent.buttons, | ||
| ctrlKey = domEvent.ctrlKey, | ||
| type = domEvent.type; | ||
| var isTouch = type === 'touchstart' || type === 'touchmove'; | ||
| - var isPrimaryMouseDown = type === 'mousedown' && (button === 0 || buttons === 1); | ||
| + var isPrimaryMouseDown = type === 'mousedown' && (button === 0 || buttons === 1 || buttons === 2); | ||
| var isPrimaryMouseMove = type === 'mousemove' && buttons === 1; | ||
| var noModifiers = altKey === false && ctrlKey === false; | ||
| if (isTouch || isPrimaryMouseDown && noModifiers || isPrimaryMouseMove && noModifiers) { |
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
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
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
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
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
Oops, something went wrong.