-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat: Integrate report fields with backend #34483
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
0f25f75
feat: save the report fields in backend
allroundexperts e089455
fix: revert canUseReportField beta
allroundexperts 04f4296
Merge branch 'main' into feat-34198
allroundexperts 7532fff
fix: lint errors
allroundexperts c91cde9
Merge branch 'main' into feat-34198
allroundexperts 389569d
Merge branch 'main' into feat-34198
allroundexperts b0f6f9b
include the whole reportfield object in the report
allroundexperts 827be79
merge with main
allroundexperts 06b2b16
create new types for the write commands
allroundexperts b58d85b
fix lint issues
allroundexperts 19cafde
fix: typechecks
allroundexperts 72b68c9
fix: remove leftover code
allroundexperts cd576d8
fix: update recently used field implementation
allroundexperts 623d1c2
fix: merge with main
allroundexperts 022efe3
fix: minor refactors to function names
allroundexperts db3738d
fix: lint issues
allroundexperts d0db92f
fix: use ucfirst str lib function and handle more lint issues
allroundexperts a761eb2
merge with main
allroundexperts 0c9939a
fix: include the whole report field object in the set report field call
allroundexperts File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
type SetReportFieldParams = { | ||
reportID: string; | ||
reportFields: string; | ||
}; | ||
|
||
export default SetReportFieldParams; |
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,6 @@ | ||
type SetReportNameParams = { | ||
reportID: string; | ||
reportName: string; | ||
}; | ||
|
||
export default SetReportNameParams; |
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.
Oops, something went wrong.
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.
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.
Should Custom report name field necessarily be a formula?
We have an issue here #49077. The bug here is if we set the custom report name as some text string instead of a formula, backend returns the type of the title field as
text
. Then this check fails andTitle
field shows up in the report though it should not show up here as per this codeApp/src/components/ReportActionItem/MoneyReportView.tsx
Lines 108 to 109 in 1354957
Can you please help here?
@thienlnam @allroundexperts @jjcoffee