fix(notebook): fix run button disable/enable (#4422)

Author: appletreeisyellow

src/flows/components/header/Submit.tsx

@@ -19,7 +19,7 @@ export const Submit: FC = () => {
   const {cancel} = useContext(QueryContext)
   const {generateMap, queryAll, status} = useContext(FlowQueryContext)
 
-  const hasQueries = generateMap().filter(s => !!s.source).length > 0
+  const hasQueries = generateMap(true).filter(s => !!s.source).length > 0
 
   const handleSubmit = () => {
     event('Notebook Submit Button Clicked')

src/flows/context/flow.query.tsx

@@ -25,7 +25,7 @@ export interface Stage {
 }
 
 export interface FlowQueryContextType {
-  generateMap: () => Stage[]
+  generateMap: (doubleForceUpdate?: boolean) => Stage[]
   printMap: (id?: string) => void
   query: (text: string, override?: QueryScope) => Promise<FluxResult>
   basic: (text: string, override?: QueryScope) => any
@@ -177,15 +177,16 @@ export const FlowQueryProvider: FC = ({children}) => {
     _generateMap()
   }, [flow])
 
-  const generateMap = (): Stage[] => {
+  const generateMap = (doubleForceUpdate?: boolean): Stage[] => {
     // this is to get around an issue where a panel is added, which triggers the useEffect that updates
     // _map.current and a rerender that updates the panel view components within the same render cycle
     // leading to a panel on the list without a corresponding map entry
     const forceUpdate =
       (flow?.data?.allIDs ?? []).join(' ') !==
       (_map.current ?? []).map(m => m.id).join(' ')
 
-    if (forceUpdate) {
+    if (forceUpdate || doubleForceUpdate) {
+      // doubleForceUpdate is used to resolve react life cycle issue
       _generateMap()
     }