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
This PR removes the 'ordering' param from being set in the front end, and the backend code that filters this param, because it is not used for the tables in /administration. It duplicates information that already exists in sortBy and descending.
Test the sortBy feature by toggling ascending and descending on various table columns. This should work with no issues on both Channels and Users
Comments
I did not see any issues with removing this and I find both the front end and the back end seem to be working as expected with manual testing. It is possible that there are issues with this approach that I did not foresee, so any feedback, especially regarding the backend, would be appreciate.
Hi @jredrejo I have removed the code in that function and I think it is working fine, but if you see any problems, please just let me know and I can adjust. Thank you!
Hi @jredrejo I have removed the code in that function and I think it is working fine, but if you see any problems, please just let me know and I can adjust. Thank you!
Your code will work without problems, I would have done it differently, but the logic is fine, thanks!
This file contains hidden or 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
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.
Description
This PR removes the 'ordering' param from being set in the front end, and the backend code that filters this param, because it is not used for the tables in
/administration. It duplicates information that already exists insortByanddescending.Issue Addressed (if applicable)
Addresses issues discussed in PR 2617
Before/After Screenshots (if applicable)
Before - information duplicated:

After - ordering not passed in URL params:

Steps to Test
/administrationpageComments
I did not see any issues with removing this and I find both the front end and the back end seem to be working as expected with manual testing. It is possible that there are issues with this approach that I did not foresee, so any feedback, especially regarding the backend, would be appreciate.