Fix double initialization with Check-or-Listen and mutex#9
Fix double initialization with Check-or-Listen and mutex#9google-labs-jules[bot] wants to merge 2 commits intomainfrom
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Implemented the Check-or-Listen pattern in
static/app.jsto prevent double initialization of the application.isInitializedboolean flag as a mutex in thesetupfunction.initto check and set the mutex.onMountedto remove thesetTimeoutfallback and unconditionally adding the event listener. Instead, it now checkswindow.pywebviewfirst, callinginitif present, or adding thepywebviewreadylistener if not.PR created automatically by Jules for task 1504147922092227330 started by @OsakaLOOP