-
Notifications
You must be signed in to change notification settings - Fork 7
Enhanced sort feature to enable user to click on the column header th… #76
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
base: develop
Are you sure you want to change the base?
Enhanced sort feature to enable user to click on the column header th… #76
Conversation
prakashchoudhary07
left a comment
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.
LGTM 🚀
| /> | ||
| )} | ||
|
No newline at end of file |
||
| return <Table featureFlags={featureFlags} headers={headers} />; |
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.
can we just make use of arrow function here? No need to write return explicitly
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.
Same is followed everywhere. This is not a change from this PR. It shows it changed because i ran perttier. Let me know if you still need me to change it because all components follow the same
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.
Ok, we can change this to arrow function
| ? a[key].toUpperCase() : a[key]; | ||
| const varB = (typeof b[key] === 'string') | ||
| ? b[key].toUpperCase() : b[key]; | ||
| const varA = typeof a[key] === "string" ? a[key].toUpperCase() : a[key]; |
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.
Can we have better naming for variable varA and varB doesn't describe it's purpose
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.
Hi @DeRaowl this is a comparator function. What do you think would be better? Since those are keys can i name them key1 and key2?
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.
Ok instead you can just add small comment saying what these variables are
| /> | ||
| )} | ||
|
No newline at end of file |
||
| return <Table featureFlags={featureFlags} headers={headers} />; |
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.
Ok, we can change this to arrow function
| ? a[key].toUpperCase() : a[key]; | ||
| const varB = (typeof b[key] === 'string') | ||
| ? b[key].toUpperCase() : b[key]; | ||
| const varA = typeof a[key] === "string" ? a[key].toUpperCase() : a[key]; |
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.
Ok instead you can just add small comment saying what these variables are
Fixes (#69)
Enhancement
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test Configuration:
Checklist: