-
Notifications
You must be signed in to change notification settings - Fork 24
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
psp-7598 | Properties list view filter by ownership #3781
Conversation
FuriousLlama
commented
Feb 9, 2024
✅ No secrets were detected in the code. |
1 similar comment
✅ No secrets were detected in the code. |
@FuriousLlama backend build failing, frontend tests failing. |
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.
I'm a little nervous about these map deletions since mapping errors only show up at runtime. Since this is a release sprint, are you 100% confident these deletions are safe?
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.
Yes, given that the model it was mapping was deleted I have confidence it was not being used anywhere else, and therefore, not mapped
{ | ||
if (tempSort[i].StartsWith("Location")) | ||
{ | ||
tempSort[i] = tempSort[i].Replace("Location", "Address.MunicipalityName"); |
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.
I can't check the story, but are we sure location maps to municipality (I know we also have a general location field in the db)
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.
{ | ||
// The order will affect the display in the frontend. For now in alphabetical order. | ||
// i.e. [Core Inventory, Disposed, Other Interest, Property of Interest] | ||
var direction = this.Sort[i].Split(' ')[1]; |
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.
is this safe (ie. we always have a direction of asc or desc)?
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.
yes, the sort expects a direction to be able to be process later
@@ -2,6 +2,7 @@ | |||
using System.Linq; | |||
using System.Linq.Expressions; | |||
using System.Reflection; | |||
using DocumentFormat.OpenXml.Office2010.Excel; |
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.
I get this sometimes too, but I'm pretty sure this is not needed.
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.
weird, i've cleansed up other instances of it.
if (orderExpression != null) | ||
{ | ||
var genericMethod = OrderByMethod.MakeGenericMethod(typeof(T), rType); | ||
var genericMethod = orderMethod.MakeGenericMethod(typeof(T), rType); |
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.
oh right, I forgot about this generic sort implementation we have.
@@ -27,4 +29,5 @@ export const defaultPropertyFilter: IPropertyFilter = { | |||
longitude: '', | |||
page: undefined, | |||
quantity: undefined, | |||
ownership: 'isCoreInventory,isPropertyOfInterest,isOtherInterest', |
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.
isDisposed?
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.
Not part of the default set, per the story definition.
|
||
const [pageSize, setPageSize] = useState(10); | ||
const [pageIndex, setPageIndex] = useState(0); | ||
const [pageCount, setPageCount] = useState(0); | ||
const [totalItems, setTotalItems] = useState(0); | ||
const [sort, setSort] = useState<TableSort<IProperty>>({}); | ||
const [sort, setSort] = useState<TableSort<any>>({}); |
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.
are they <any> 's in this file intentional?
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.
yeah I was matching the other definitions. I made it Api_Property instead
Finished code review, but will hold off on approval until I can actually run the code. |
✅ No secrets were detected in the code. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## dev #3781 +/- ##
==========================================
- Coverage 75.75% 75.69% -0.06%
==========================================
Files 1448 1446 -2
Lines 38076 38080 +4
Branches 7136 7154 +18
==========================================
- Hits 28844 28826 -18
- Misses 8949 8967 +18
- Partials 283 287 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
approving based on checking out the PR, please see comments.
✅ No secrets were detected in the code. |
✅ No secrets were detected in the code. |
1 similar comment
✅ No secrets were detected in the code. |