Closed Jamie9192 closed 1 month ago
Testing shows major improvement only importing Functions. Shared seems to be the main cause of large object. This being client side testing only.
For reference: a localised empty table uses 255KiB I pasted wrong one for shared vehicles - it was alot lower
@Jamie9192 Could you just add the code to the export with an early return of the full core object if no filters
@Jamie9192 Could you just add the code to the export with an early return of the full core object if no filters
Sure, but the filter function is not just for the core object, and could potentially be used in other resources
The only thing i would maybe like to see, is the filter function itself being moved to QBShared, as maybe a:
QBShared.FilterTable
This would make sense more so if the core exports were shared, but they are separated, and Shared holds data rather than functions.
As it is a function, I believe its best to be added as such
This PR has had 60 days of inactivity & will close within 7 days
Pass the structure of QBCore, making the value you want equal either "all" or true. Examples in main.lua on client and server side
Description
Adds ability to filter the core object when importing. Thus reducing memory usage. Fixes: importing large object of unneccessary data when not required
Checklist