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
{{ message }}
This repository has been archived by the owner on Jul 26, 2024. It is now read-only.
Describe the solution and problem
This PR solves an issue with slow loading eel applications by offering the developer the option to exclude file paths from the EXPOSED_JS_FUNCTIONS scan.
Instead of just scanning all .html, .js and .txt files, the developer can exclude file paths containing any of the strings passed trough the exclude_path parameter.
In a typical html template, there are lots of javascript files that add GUI functionalities, and in one case this added up to 120 seconds when using the current init command.
eel.init('web') took 122.60855889320374 seconds
assuming all external javascript files are in the web/plugins directory, changing to the new option:
eel.init('web', exclude_path=['web/plugins']) took 1.013951301574707 seconds
Credits go to:
@savelkouls
Describe the solution and problem
This PR solves an issue with slow loading eel applications by offering the developer the option to exclude file paths from the EXPOSED_JS_FUNCTIONS scan.
Instead of just scanning all .html, .js and .txt files, the developer can exclude file paths containing any of the strings passed trough the exclude_path parameter.
In a typical html template, there are lots of javascript files that add GUI functionalities, and in one case this added up to 120 seconds when using the current init command.
eel.init('web') took 122.60855889320374 seconds
assuming all external javascript files are in the web/plugins directory, changing to the new option:
eel.init('web', exclude_path=['web/plugins']) took 1.013951301574707 seconds
python-eel#697
The text was updated successfully, but these errors were encountered: