-
Notifications
You must be signed in to change notification sett 8000 ings - Fork 748
Resource List Stops After 4th Entry - Additional Resources Exist But Are Not Listed #1959
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
Comments
Just noticed it seems to be a caching issue - in the BROWSER! I would expect api calls not to be cached at all... |
Is this what you mean? I wasn't able to reproduce with the same versions. Screen.Recording.2025-04-23.at.9.36.09.AM.mov |
Disclaimer: First time user The very first form I tried to create, on the latest build, following instructions directly out of this repo, not trying anything fancy, just rip it and zip it. The form did not show up in the form list. No matter if I refreshed, cleared cache, or restarted docker. Then I arbitrarily made a handful more and randomly all the ones that were missing showed up. Now what I am noticing is that sometimes entries in either Resource or Forms will fail to update. And in some cases, after being deleted, will fail to leave this list -- but it's obvious that they're being deleted behind the scenes, if you click on a form/resource it will take you to an empty container, they're just not being properly released from the ui. |
@phatmandrake |
Describe the bug
Fresh install of the docker-compose on local machine. There are 2 predefined resources (User, Admin). I can add resources and upto 4 are listed. Any additional resource created does exist in the API and can be addressed in the app (using its ID), but is not listed in the Resource List
Version/Branch
App Version: v4.5.0-rc.6, Renderer: v5.1.0-rc.15
React: v18.2.0, React Module: v6.0.2-rc.2
To Reproduce
Steps to reproduce the behavior: see above
Expected behavior
I expect all resources listed
The text was updated successfully, but these errors were encountered: