[ACS-10083] Filter not behaving correctly in file and site

[rmnvch]

JIRA ticket link or changeset's description
https://hyland.atlassian.net/browse/ACS-10083

relates to:
ADF PR:
Alfresco/alfresco-ng2-components#11237

blocks ADW PR:
https://github.com/Alfresco/alfresco-applications/pull/1258

[rmnvch]

@AleksanderSklorz ,
for some reason your initial comment has gone. The issue was connected to lag after page reload with queryParams - filters are applied after initial API call:

Screen.Recording.2025-10-06.at.13.07.47.mov

So the reason for that is that we have 2 APIs to work with folders - Search API and Nodes API ('/nodes/{nodeId}/children' endpoint). I've examined several options:

• Migrate to Nodes API fully. It can be used with folders/files filtering, but Nodes API has limits in terms of filtering be text queries - it supports only EQUALS operator in queries ('where' parameter) and cannot be used to filter according text queries - 'LIKE' or 'CONTAINS' are not supported as confirmed with BE team.
• Extend loader indicator. Filters are initiated after initial data is loaded, it means that table should be showed to make additional request.

I suggest create dedicated ticket for exploring option with additional loader indicator. It would require some refactoring

cc @MichalKinas

[AleksanderSklorz]

@AleksanderSklorz , for some reason your initial comment has gone. The issue was connected to lag after page reload with queryParams - filters are applied after initial API call:

Screen.Recording.2025-10-06.at.13.07.47.mov
So the reason for that is that we have 2 APIs to work with folders - Search API and Nodes API ('/nodes/{nodeId}/children' endpoint). I've examined several options:

• Migrate to Nodes API fully. It can be used with folders/files filtering, but Nodes API has limits in terms of filtering be text queries - it supports only EQUALS operator in queries ('where' parameter) and cannot be used to filter according text queries - 'LIKE' or 'CONTAINS' are not supported as confirmed with BE team.
• Extend loader indicator. Filters are initiated after initial data is loaded, it means that table should be showed to make additional request.

I suggest create dedicated ticket for exploring option with additional loader indicator. It would require some refactoring

cc @MichalKinas

Hi @rmnvch. My comment is still but not here. It's in alfresco-applications repository:
https://github.com/Alfresco/alfresco-applications/pull/1258#issuecomment-3355208593

Regarding to solution: by "extend loader indicator" you mean adding something like "loading spinner" there, right? Yes, it makes sense for me. If you need more time you can do it as part of that PR, it's fine or you can create separate ticket if you prefer do it as separated one. In case you want to do it as separated task then please create jira task and add link to that task as comment here in PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud