feat: move tax types grid to mui#931
Open
priscila-moneo wants to merge 3 commits into
Open
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR moves tax-type management to an in-place modal: actions gain term/pagination/sort, the reducer stores pagination state, the form is rebuilt with Formik+Yup and MUI, a TaxTypePopup dialog wraps the form, the list page uses hooks + MuiTable and opens the modal for add/edit, and routing/layout files are updated. ChangesTax Type Management Modal Refactor
Estimated code review effort🎯 4 (Complex) | ⏱️ ~50 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
santipalenque
left a comment
santipalenque
left a comment
There was a problem hiding this comment.
overall looks great, just a couple of requests
| `${window.API_BASE_URL}/api/v1/summits/${currentSummit.id}/tax-types`, | ||
| authErrorHandler, | ||
| { order, orderDir } | ||
| { order: normalizedOrder, orderDir, page, perPage, term } |
There was a problem hiding this comment.
the order stored in reducer should be order not normalizedOrder, the latter is just to send to API
| }) => { | ||
| const [entity, setEntity] = useState({ ...entityProp }); | ||
| const [errors, setErrors] = useState(errorsProp); | ||
| const prevEntityRef = useRef(entityProp); |
There was a problem hiding this comment.
no need for this, you can accomplish the same with just an useEffect and putting the entity in dependencies
| } | ||
| } | ||
| <Switch> | ||
| <Route strict exact path={match.url} component={TaxTypeListPage} /> |
There was a problem hiding this comment.
if we are only having one route then there is no need for a tax-type-layout, we can just move this route to the parent layout and get rid of it
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
src/pages/taxes/tax-type-list-page.js (1)
57-61: 💤 Low valueConsider keying the effect on
currentSummit?.id.Depending on
currentSummitre-runs the fetch whenever any field of the summit object changes reference. Since the only thing this effect cares about is the active summit identity, using[currentSummit?.id]is cheaper and matches the guard on line 58.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/taxes/tax-type-list-page.js` around lines 57 - 61, The useEffect currently depends on the entire currentSummit object causing unnecessary re-runs; change its dependency array to depend only on currentSummit?.id and keep the existing guard so the effect only triggers when the summit identity changes—update the useEffect dependency from [currentSummit] to [currentSummit?.id] for the effect that calls getTaxTypes(term, currentPage, perPage, order, orderDir).src/actions/tax-actions.js (1)
82-85: 💤 Low valueDead
nullchecks on guaranteed non-null values.
normalizedOrderis always assigned to eitherorderor"name"via the ternary on lines 59–61, andorderDirhas a default value (DEFAULT_ORDER_DIR). Both will never benull, so theif (normalizedOrder != null && orderDir != null)guard is dead code. You can drop the conditional and always setparams.order.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/actions/tax-actions.js` around lines 82 - 85, The null-check guard around setting params.order is dead because normalizedOrder is always assigned (either order or "name") and orderDir defaults to DEFAULT_ORDER_DIR; remove the surrounding if and always assign params.order by computing orderDirSign (using orderDir === 1 ? "" : "-") and setting params.order = `${orderDirSign}${normalizedOrder}` within the same block (refer to normalizedOrder, orderDir, DEFAULT_ORDER_DIR, orderDirSign, and params.order).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/forms/tax-type-form.js`:
- Around line 23-46: The useEffect in TaxTypeForm currently depends on local
state (entity, errors) causing cleared local errors to be clobbered by
errorsProp; split into two effects: 1) a useEffect that runs when errorsProp
changes to call scrollToError(errorsProp) and, if needed, setErrors(errorsProp)
only when shallowEqual(errors, errorsProp) is false (depend only on errorsProp
and errorsProp reference change), and 2) a useEffect that syncs entity from
entityProp (compare entityProp.id to entity.id and call
setEntity({...entityProp}) when entityProp.id changes) that depends only on
entityProp; remove entity and errors from the dependency array of the original
combined effect so local handleChange updates to errors are not overwritten.
In `@src/pages/taxes/tax-type-list-page.js`:
- Around line 92-96: The modal is being closed in the finally block of
handleSave which hides validation errors on failure; instead, remove
setShowTaxTypeModal(false) from the finally and call it only on successful save
inside the promise resolution (the .then chain after saveTaxType), e.g., after
getTaxTypes completes, call setShowTaxTypeModal(false); leave rejections
untouched so currentTaxTypeErrors (and any error UI) remain visible when
saveTaxType rejects.
---
Nitpick comments:
In `@src/actions/tax-actions.js`:
- Around line 82-85: The null-check guard around setting params.order is dead
because normalizedOrder is always assigned (either order or "name") and orderDir
defaults to DEFAULT_ORDER_DIR; remove the surrounding if and always assign
params.order by computing orderDirSign (using orderDir === 1 ? "" : "-") and
setting params.order = `${orderDirSign}${normalizedOrder}` within the same block
(refer to normalizedOrder, orderDir, DEFAULT_ORDER_DIR, orderDirSign, and
params.order).
In `@src/pages/taxes/tax-type-list-page.js`:
- Around line 57-61: The useEffect currently depends on the entire currentSummit
object causing unnecessary re-runs; change its dependency array to depend only
on currentSummit?.id and keep the existing guard so the effect only triggers
when the summit identity changes—update the useEffect dependency from
[currentSummit] to [currentSummit?.id] for the effect that calls
getTaxTypes(term, currentPage, perPage, order, orderDir).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9640f65d-8b34-4dd1-bd06-09cb030783d6
📒 Files selected for processing (8)
src/actions/tax-actions.jssrc/components/forms/tax-type-form.jssrc/layouts/summit-id-layout.jssrc/layouts/tax-type-layout.jssrc/pages/taxes/edit-tax-type-page.jssrc/pages/taxes/popup/tax-type-popup.jssrc/pages/taxes/tax-type-list-page.jssrc/reducers/taxes/tax-type-list-reducer.js
💤 Files with no reviewable changes (2)
- src/pages/taxes/edit-tax-type-page.js
- src/layouts/tax-type-layout.js
| path={`${match.url}/tax-types`} | ||
| render={(routeProps) => ( | ||
| <> | ||
| <Breadcrumb |
There was a problem hiding this comment.
this is the onlyu route, the breadcrumb can go in the Page component
| const RegFeedMetadataLayout = React.lazy(() => | ||
| import("./reg-feed-metadata-layout") | ||
| ); | ||
| const RestrictedTaxTypeListPage = Restrict(TaxTypeListPage, "taxes"); |
There was a problem hiding this comment.
you can add the Restrict in the page component export: example
| newEntity[id] = value; | ||
| this.setState({ entity: newEntity, errors: newErrors }); | ||
| } | ||
| if (ev.target.type === "checkbox") { |
There was a problem hiding this comment.
doesn't look like we have any checkboxes or datetime inputs in this form, do we need this ?
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
552e588 to
e8c64c4
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/forms/tax-type-form.js`:
- Around line 128-184: The form is a real <form> but Enter triggers native
submit because handleSubmit is only wired to the Button onClick; add an onSubmit
prop to the form element (the Box with component="form") that calls handleSubmit
and ensures it does event.preventDefault(), and then remove (or keep but no-op)
the Button's onClick to avoid duplicate handling; update the form wiring so
handleSubmit handles the submit event from the form (signature event => {
event.preventDefault(); ... }) and keep the Button as type="submit".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e5631419-7127-47c9-957b-cee70da10552
📒 Files selected for processing (8)
src/actions/tax-actions.jssrc/components/forms/tax-type-form.jssrc/layouts/summit-id-layout.jssrc/layouts/tax-type-layout.jssrc/pages/taxes/edit-tax-type-page.jssrc/pages/taxes/popup/tax-type-popup.jssrc/pages/taxes/tax-type-list-page.jssrc/reducers/taxes/tax-type-list-reducer.js
💤 Files with no reviewable changes (2)
- src/pages/taxes/edit-tax-type-page.js
- src/layouts/tax-type-layout.js
✅ Files skipped from review due to trivial changes (1)
- src/reducers/taxes/tax-type-list-reducer.js
🚧 Files skipped from review as they are similar to previous changes (3)
- src/pages/taxes/popup/tax-type-popup.js
- src/actions/tax-actions.js
- src/pages/taxes/tax-type-list-page.js
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
e8c64c4 to
9e52a0a
Compare
santipalenque
left a comment
santipalenque
left a comment
There was a problem hiding this comment.
Very clean, good job!
Just need confirmation from @smarcet on the forms migration
|
|
||
| return ( | ||
| <Box component="form" onSubmit={handleSubmit}> | ||
| <input type="hidden" id="id" value={entity.id} /> |
| onSubmit | ||
| }) => { | ||
| const [entity, setEntity] = useState({ ...entityProp }); | ||
| const [errors, setErrors] = useState(errorsProp); |
There was a problem hiding this comment.
@smarcet this legacy approach relies on the API for input validation, should we migrate to formik/yup while migrating to MUI ?
There was a problem hiding this comment.
yes we need to use formik / yup as we are doing with the rest of the MUI forms
smarcet
requested changes
May 20, 2026
smarcet
left a comment
smarcet
left a comment
There was a problem hiding this comment.
@priscila-moneo please review comments about formik/yup
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
9e52a0a to
dd302b2
Compare
Author
@smarcet Ready! |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/reducers/taxes/tax-type-list-reducer.js (1)
64-70:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win
totalTaxTypesnot decremented on delete.When a tax type is deleted,
taxTypesis filtered buttotalTaxTypesremains unchanged. This causes a mismatch between the displayed count and actual items. The list page should refresh after delete (as noted in that file's review) to get the correct count from the server, or the reducer could decrementtotalTaxTypeshere.🔧 Option: Decrement count in reducer
case TAX_TYPE_DELETED: { const { taxTypeId } = payload; return { ...state, - taxTypes: state.taxTypes.filter((t) => t.id !== taxTypeId) + taxTypes: state.taxTypes.filter((t) => t.id !== taxTypeId), + totalTaxTypes: state.totalTaxTypes - 1 }; }Alternatively, ensure the list page refreshes after delete to fetch the updated count from the server.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/reducers/taxes/tax-type-list-reducer.js` around lines 64 - 70, In the TAX_TYPE_DELETED case of the reducer update both the taxTypes array and totalTaxTypes: after filtering out the deleted item (taxTypes.filter(...)) decrement totalTaxTypes (e.g., totalTaxTypes - 1 or set to Math.max(0, state.totalTaxTypes - 1)) so the count stays in sync with the removed item; ensure you return a new state object and guard against going below zero.
🧹 Nitpick comments (1)
src/pages/taxes/popup/tax-type-popup.js (1)
39-46: 💤 Low valueRemove unused
errorsprop from TaxTypeForm.
TaxTypeFormwas migrated to Formik/Yup validation and no longer accepts anerrorsprop. The prop is being passed here (line 42) but will be ignored.🧹 Suggested cleanup
<TaxTypeForm entity={entity} currentSummit={currentSummit} - errors={errors} onTicketLink={onTicketLink} onTicketUnLink={onTicketUnLink} onSubmit={onSubmit} />Also remove the
errorsprop fromTaxTypePopuppropTypes/defaultProps and the component signature since it's no longer needed.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/taxes/popup/tax-type-popup.js` around lines 39 - 46, Remove the unused errors prop passed to TaxTypeForm: delete the errors={errors} prop in the TaxTypeForm JSX and then remove the now-unused errors prop from the TaxTypePopup component's props/signature and from its propTypes and defaultProps declarations; ensure no remaining references to errors exist in TaxTypePopup so ESLint won't complain and Formik/Yup validation remains authoritative in TaxTypeForm.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/pages/taxes/tax-type-list-page.js`:
- Around line 65-67: handleDelete currently just calls deleteTaxType(taxTypeId)
and doesn't update pagination info; after deletion you must refresh the list and
adjust the current page when needed. Change handleDelete to await the
deleteTaxType call (or use its returned promise) and then either dispatch the
action that reloads the list (e.g., fetchTaxTypes or loadTaxTypes) for the
current page, and if totalTaxTypes % pageSize === 1 and currentPage > 1
decrement currentPage before reloading so users on the last-item page are moved
back; reference handleDelete, deleteTaxType, totalTaxTypes, pageSize/currentPage
(or your pagination state), and the reducer action TAX_TYPE_DELETED to implement
this flow.
---
Outside diff comments:
In `@src/reducers/taxes/tax-type-list-reducer.js`:
- Around line 64-70: In the TAX_TYPE_DELETED case of the reducer update both the
taxTypes array and totalTaxTypes: after filtering out the deleted item
(taxTypes.filter(...)) decrement totalTaxTypes (e.g., totalTaxTypes - 1 or set
to Math.max(0, state.totalTaxTypes - 1)) so the count stays in sync with the
removed item; ensure you return a new state object and guard against going below
zero.
---
Nitpick comments:
In `@src/pages/taxes/popup/tax-type-popup.js`:
- Around line 39-46: Remove the unused errors prop passed to TaxTypeForm: delete
the errors={errors} prop in the TaxTypeForm JSX and then remove the now-unused
errors prop from the TaxTypePopup component's props/signature and from its
propTypes and defaultProps declarations; ensure no remaining references to
errors exist in TaxTypePopup so ESLint won't complain and Formik/Yup validation
remains authoritative in TaxTypeForm.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: eede6858-fedc-425f-96ff-43d327e0c689
📒 Files selected for processing (8)
src/actions/tax-actions.jssrc/components/forms/tax-type-form.jssrc/layouts/summit-id-layout.jssrc/layouts/tax-type-layout.jssrc/pages/taxes/edit-tax-type-page.jssrc/pages/taxes/popup/tax-type-popup.jssrc/pages/taxes/tax-type-list-page.jssrc/reducers/taxes/tax-type-list-reducer.js
💤 Files with no reviewable changes (2)
- src/pages/taxes/edit-tax-type-page.js
- src/layouts/tax-type-layout.js
Signed-off-by: Priscila Moneo <[email protected]>
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
dd302b2 to
ffb91e9
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/pages/taxes/popup/__tests__/tax-type-popup.test.js (1)
76-96: ⚡ Quick winTest doesn't match its description.
The test is named "does not re-trigger onSubmit while a save is in flight" but it never attempts a second click on the submit button. It only verifies that the button becomes disabled and
onSubmitwas called once.Consider either adding a second click attempt to match the description, or renaming the test to reflect what it actually verifies.
🔧 Option 1: Add second click attempt to match test name
await waitFor(() => expect(screen.getByRole("button", { name: "submit-form" })).toBeDisabled() ); + + // Attempt to click again while disabled + await userEvent.click(screen.getByRole("button", { name: "submit-form" })); + expect(onSubmit).toHaveBeenCalledTimes(1);Option 2: Rename test to match current behavior
- it("does not re-trigger onSubmit while a save is in flight", async () => { + it("disables submit button to prevent re-trigger while save is pending", async () => {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/taxes/popup/__tests__/tax-type-popup.test.js` around lines 76 - 96, The test name says "does not re-trigger onSubmit while a save is in flight" but never tries a second submit; update the test to actually attempt a second click: after the first click and the waitFor that verifies the submit button is disabled and expect(onSubmit).toHaveBeenCalledTimes(1), add a second userEvent.click(screen.getByRole("button", { name: "submit-form" })) and then assert onSubmit remains called once (expect(onSubmit).toHaveBeenCalledTimes(1)); use the existing resolveSave/act block to complete the in-flight promise as before. This change involves the test function (the it block), the onSubmit mock usage, renderPopup call, and the userEvent.click/screen.getByRole assertions.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@src/pages/taxes/popup/__tests__/tax-type-popup.test.js`:
- Around line 76-96: The test name says "does not re-trigger onSubmit while a
save is in flight" but never tries a second submit; update the test to actually
attempt a second click: after the first click and the waitFor that verifies the
submit button is disabled and expect(onSubmit).toHaveBeenCalledTimes(1), add a
second userEvent.click(screen.getByRole("button", { name: "submit-form" })) and
then assert onSubmit remains called once
(expect(onSubmit).toHaveBeenCalledTimes(1)); use the existing resolveSave/act
block to complete the in-flight promise as before. This change involves the test
function (the it block), the onSubmit mock usage, renderPopup call, and the
userEvent.click/screen.getByRole assertions.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 37b63957-b4c8-4305-a459-3f242a42b4ae
📒 Files selected for processing (12)
src/actions/__tests__/tax-actions.test.jssrc/actions/tax-actions.jssrc/components/forms/tax-type-form.jssrc/i18n/en.jsonsrc/layouts/summit-id-layout.jssrc/layouts/tax-type-layout.jssrc/pages/taxes/__tests__/tax-type-list-page.test.jssrc/pages/taxes/edit-tax-type-page.jssrc/pages/taxes/popup/__tests__/tax-type-popup.test.jssrc/pages/taxes/popup/tax-type-popup.jssrc/pages/taxes/tax-type-list-page.jssrc/reducers/taxes/tax-type-list-reducer.js
💤 Files with no reviewable changes (2)
- src/pages/taxes/edit-tax-type-page.js
- src/layouts/tax-type-layout.js
✅ Files skipped from review due to trivial changes (1)
- src/i18n/en.json
🚧 Files skipped from review as they are similar to previous changes (6)
- src/reducers/taxes/tax-type-list-reducer.js
- src/pages/taxes/popup/tax-type-popup.js
- src/components/forms/tax-type-form.js
- src/layouts/summit-id-layout.js
- src/actions/tax-actions.js
- src/pages/taxes/tax-type-list-page.js
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
727b9af to
21118c0
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/actions/__tests__/tax-actions.test.js (1)
55-61: ⚡ Quick winAssert the resolved payload contract, not only Promise type.
These tests currently verify only that a Promise is returned, but not that
saveTaxTyperesolves with the request payload (the new behavior this PR introduces).Proposed test update
- describe("create path (entity has no id)", () => { - it("returns a Promise", () => { + describe("create path (entity has no id)", () => { + it("returns the resolved payload", async () => { const store = mockStore(storeState); - const result = store.dispatch( - saveTaxType({ name: "VAT", rate: 20, tax_id: "V1" }) - ); - expect(result).toBeInstanceOf(Promise); + await expect( + store.dispatch(saveTaxType({ name: "VAT", rate: 20, tax_id: "V1" })) + ).resolves.toEqual({ response: {} }); }); @@ - describe("update path (entity has id)", () => { - it("returns a Promise", () => { + describe("update path (entity has id)", () => { + it("returns the resolved payload", async () => { const store = mockStore(storeState); - const result = store.dispatch( - saveTaxType({ id: 1, name: "VAT", rate: 20, tax_id: "V1" }) - ); - expect(result).toBeInstanceOf(Promise); + await expect( + store.dispatch(saveTaxType({ id: 1, name: "VAT", rate: 20, tax_id: "V1" })) + ).resolves.toEqual({ response: {} }); });Also applies to: 78-84
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/actions/__tests__/tax-actions.test.js` around lines 55 - 61, The test currently only asserts that store.dispatch(saveTaxType(...)) returns a Promise; update it to assert the resolved payload matches the request payload by either awaiting the dispatched promise or using Jest's .resolves matcher; specifically, call store.dispatch(saveTaxType({ name: "VAT", rate: 20, tax_id: "V1" })) and assert the promise resolves to an object equal to that payload (or to the expected shape that includes it). Apply the same change to the other test case referenced (the one around the saveTaxType dispatch at the later block) so both tests verify the resolved value rather than only Promise type.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@src/actions/__tests__/tax-actions.test.js`:
- Around line 55-61: The test currently only asserts that
store.dispatch(saveTaxType(...)) returns a Promise; update it to assert the
resolved payload matches the request payload by either awaiting the dispatched
promise or using Jest's .resolves matcher; specifically, call
store.dispatch(saveTaxType({ name: "VAT", rate: 20, tax_id: "V1" })) and assert
the promise resolves to an object equal to that payload (or to the expected
shape that includes it). Apply the same change to the other test case referenced
(the one around the saveTaxType dispatch at the later block) so both tests
verify the resolved value rather than only Promise type.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 205836ed-0636-4fb0-818e-fe8e15dea024
📒 Files selected for processing (8)
src/actions/__tests__/tax-actions.test.jssrc/actions/tax-actions.jssrc/components/forms/tax-type-form.jssrc/i18n/en.jsonsrc/pages/taxes/__tests__/tax-type-list-page.test.jssrc/pages/taxes/popup/__tests__/tax-type-popup.test.jssrc/pages/taxes/popup/tax-type-popup.jssrc/pages/taxes/tax-type-list-page.js
✅ Files skipped from review due to trivial changes (1)
- src/i18n/en.json
🚧 Files skipped from review as they are similar to previous changes (5)
- src/pages/taxes/popup/tests/tax-type-popup.test.js
- src/pages/taxes/tests/tax-type-list-page.test.js
- src/pages/taxes/popup/tax-type-popup.js
- src/components/forms/tax-type-form.js
- src/pages/taxes/tax-type-list-page.js
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
21118c0 to
0ffda96
Compare
Signed-off-by: Priscila Moneo <[email protected]>
priscila-moneo
force-pushed
the
feature/move-tax-types-grid-mui
branch
from
0ffda96 to
b8f16f4
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
ref: https://app.clickup.com/t/86b9tggfp
Summary by CodeRabbit
New Features
Refactor
Tests
Localization