You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
After the updates to how we name collections, users can no longer search for schemas in the capture edit search box.
It would be ideal to change how we show collection names in that portion of the UI to show both the schema and table name so that users could see and search for schemas as well as table names.
The text was updated successfully, but these errors were encountered:
We'll need to see how this can work with the MUI table we're using to show the list. We might have to pull filtering out of the table and into stand alone code.
I think we might have to manually filter now. This will be interesting to figure out. Setting the filterModel manually does NOT make a call to the "filter changed" function. We might end up having to just manually mess with the rows data manually while altering the filter and no longer even tell MUI about the filtering.
This could end up having some weird impacts since we are using pagination. However, we use a lot of the same things on other tables so I am pretty sure it will be okay.
Bonus Points
This could be the main area where we need MUI to use eval... so without this we might find a solid way to not have it include eval at all and help increase safety a bit.
Problem
After the updates to how we name collections, users can no longer search for schemas in the capture edit search box.
It would be ideal to change how we show collection names in that portion of the UI to show both the schema and table name so that users could see and search for schemas as well as table names.
The text was updated successfully, but these errors were encountered: