-
Notifications
You must be signed in to change notification settings - Fork 181
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(fe2): Improve property name display and search functionality in filtering #2396
feat(fe2): Improve property name display and search functionality in filtering #2396
Conversation
return revitPropertyRegex.test(key) | ||
} | ||
|
||
const getPropertyName = (key: string): string => { |
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.
Seems like everywhere where we use this fn we have access to the entire filter object. If we pass that in, instead of just the key, we don't have to do the props.filters.find()
bit
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.
Passing the entire filter object introduced complexity with a fallback mechanism and error handling in title. Let me know if this is enough to stop us merging and I can take another look on Monday but I'm running out of time today
…-of-searchable-properties
…-of-searchable-properties
…-of-searchable-properties
This reverts commit 21aaabd.
Description & motivation
This PR addresses user feedback from the forums regarding the display of property names and the search functionality in our UI for Revit files. Users requested more user-friendly property names instead of raw database keys and improved search capabilities.
Changes: