prompt: Your task is to convert the following English description into an ASCII tree format.
  
  fixtures is a master directory that groups 4 subdirectories. Notable ones include flow-compat, jsx-compat, node-extensions among others.
  
  Let me break down the construction for you:
  
  In the root directory, 'flow-compat' incorporates 6 numerous subdirectories.
  At level 2, in directory path 'flow-compat / js-invalid', The 'js-invalid' container is an empty container.
  Within directory hierarchy 'flow-compat → js-valid', The 'js-valid' data structure is currently empty.
  In nested path 'flow-compat > ts-invalid', The 'ts-invalid' container is blank.
  At level 2, in directory path 'flow-compat > ts-valid', 'ts-valid' is unpopulated.
  At level 2, in directory path 'flow-compat → tsx-invalid', Inside 'tsx-invalid', you'll find it remains unused.
  In nested path 'flow-compat > tsx-valid', The 'tsx-valid' directory contains nothing at present.
  Back to the top level.
  At the top level, 'jsx-compat' keeps 4 numerous subfolders.
  Within directory hierarchy 'jsx-compat > js-valid', The 'js-valid' collection holds no subdirectories at the moment.
  Within directory hierarchy 'jsx-compat / ts-invalid', Inside 'ts-invalid', you'll find it contains no subdirectories.
  At level 2, in directory path 'jsx-compat → ts-invalid-babel-7', The 'ts-invalid-babel-7' folder is currently empty.
  At level 2, in directory path 'jsx-compat → tsx-valid', Inside 'tsx-valid', you'll find it is an empty container.
  Back to the top level.
  At the top level, 'node-extensions' shelters 10 various contained folders.
  In nested path 'node-extensions → import-in-cts', Inside 'import-in-cts', you'll find it is a vacant space.
  At level 2, in directory path 'node-extensions → import-in-mts', Inside 'import-in-mts', you'll find it lacks any subdirectories.
  At level 2, in directory path 'node-extensions → type-assertion-in-cts', 'type-assertion-in-cts' holds no subdirectories at the moment.
  In nested path 'node-extensions → type-assertion-in-mts', The 'type-assertion-in-mts' storage space has been left empty.
  At level 2, in directory path 'node-extensions > type-assertion-in-ts', 'type-assertion-in-ts' is vacant.
  At level 2, in directory path 'node-extensions → type-param-arrow-in-cts', The 'type-param-arrow-in-cts' storage space is unpopulated.
  Within directory hierarchy 'node-extensions > type-param-arrow-in-mts', The 'type-param-arrow-in-mts' storage space is devoid of content.
  At level 2, in directory path 'node-extensions > type-param-arrow-in-ts', Inside 'type-param-arrow-in-ts', you'll find it holds no subdirectories at the moment.
  At level 2, in directory path 'node-extensions > with-in-cts', The 'with-in-cts' folder is an empty container.
  In nested path 'node-extensions > with-in-mts', The 'with-in-mts' container hasn't been filled with any content.
  Back to the top level.
  At the main level, 'opts' houses 6 different nested folders.
  In nested path 'opts → allExtensions-true-isTSX-true', 'allExtensions-true-isTSX-true' holds no subdirectories at the moment.
  In nested path 'opts > allowDeclareFields', The 'allowDeclareFields' collection is currently empty.
  In nested path 'opts / ignoreExtensions', 'ignoreExtensions' is devoid of content.
  In nested path 'opts / optimizeConstEnums', 'optimizeConstEnums' remains unused.
  Within directory hierarchy 'opts > rewriteImportExtensions', The 'rewriteImportExtensions' section hasn't been filled with any content.
  Within directory hierarchy 'opts → rewriteImportExtensions-createImportExpressions', 'rewriteImportExtensions-createImportExpressions' has yet to be populated.
  Back to the top level.
  
  
  Format your response in this style:
  ```
  gradle
   +--api
   +--internal
   `--util
       `--internal
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "fixtures\n +--flow-compat\n |   +--js-invalid\n |   +--js-valid\n |   +--ts-invalid\n |   +--ts-valid\n |   +--tsx-invalid\n |   `--tsx-valid\n +--jsx-compat\n |   +--js-valid\n |   +--ts-invalid\n |   +--ts-invalid-babel-7\n |   `--tsx-valid\n +--node-extensions\n |   +--import-in-cts\n |   +--import-in-mts\n |   +--type-assertion-in-cts\n |   +--type-assertion-in-mts\n |   +--type-assertion-in-ts\n |   +--type-param-arrow-in-cts\n |   +--type-param-arrow-in-mts\n |   +--type-param-arrow-in-ts\n |   +--with-in-cts\n |   `--with-in-mts\n `--opts\n     +--allExtensions-true-isTSX-true\n     +--allowDeclareFields\n     +--ignoreExtensions\n     +--optimizeConstEnums\n     +--rewriteImportExtensions\n     `--rewriteImportExtensions-createImportExpressions", "description": "fixtures is a master directory that groups 4 subdirectories. Notable ones include flow-compat, jsx-compat, node-extensions among others.\n\nLet me break down the construction for you:\n\nIn the root directory, 'flow-compat' incorporates 6 numerous subdirectories.\nAt level 2, in directory path 'flow-compat / js-invalid', The 'js-invalid' container is an empty container.\nWithin directory hierarchy 'flow-compat \u2192 js-valid', The 'js-valid' data structure is currently empty.\nIn nested path 'flow-compat > ts-invalid', The 'ts-invalid' container is blank.\nAt level 2, in directory path 'flow-compat > ts-valid', 'ts-valid' is unpopulated.\nAt level 2, in directory path 'flow-compat \u2192 tsx-invalid', Inside 'tsx-invalid', you'll find it remains unused.\nIn nested path 'flow-compat > tsx-valid', The 'tsx-valid' directory contains nothing at present.\nBack to the top level.\nAt the top level, 'jsx-compat' keeps 4 numerous subfolders.\nWithin directory hierarchy 'jsx-compat > js-valid', The 'js-valid' collection holds no subdirectories at the moment.\nWithin directory hierarchy 'jsx-compat / ts-invalid', Inside 'ts-invalid', you'll find it contains no subdirectories.\nAt level 2, in directory path 'jsx-compat \u2192 ts-invalid-babel-7', The 'ts-invalid-babel-7' folder is currently empty.\nAt level 2, in directory path 'jsx-compat \u2192 tsx-valid', Inside 'tsx-valid', you'll find it is an empty container.\nBack to the top level.\nAt the top level, 'node-extensions' shelters 10 various contained folders.\nIn nested path 'node-extensions \u2192 import-in-cts', Inside 'import-in-cts', you'll find it is a vacant space.\nAt level 2, in directory path 'node-extensions \u2192 import-in-mts', Inside 'import-in-mts', you'll find it lacks any subdirectories.\nAt level 2, in directory path 'node-extensions \u2192 type-assertion-in-cts', 'type-assertion-in-cts' holds no subdirectories at the moment.\nIn nested path 'node-extensions \u2192 type-assertion-in-mts', The 'type-assertion-in-mts' storage space has been left empty.\nAt level 2, in directory path 'node-extensions > type-assertion-in-ts', 'type-assertion-in-ts' is vacant.\nAt level 2, in directory path 'node-extensions \u2192 type-param-arrow-in-cts', The 'type-param-arrow-in-cts' storage space is unpopulated.\nWithin directory hierarchy 'node-extensions > type-param-arrow-in-mts', The 'type-param-arrow-in-mts' storage space is devoid of content.\nAt level 2, in directory path 'node-extensions > type-param-arrow-in-ts', Inside 'type-param-arrow-in-ts', you'll find it holds no subdirectories at the moment.\nAt level 2, in directory path 'node-extensions > with-in-cts', The 'with-in-cts' folder is an empty container.\nIn nested path 'node-extensions > with-in-mts', The 'with-in-mts' container hasn't been filled with any content.\nBack to the top level.\nAt the main level, 'opts' houses 6 different nested folders.\nIn nested path 'opts \u2192 allExtensions-true-isTSX-true', 'allExtensions-true-isTSX-true' holds no subdirectories at the moment.\nIn nested path 'opts > allowDeclareFields', The 'allowDeclareFields' collection is currently empty.\nIn nested path 'opts / ignoreExtensions', 'ignoreExtensions' is devoid of content.\nIn nested path 'opts / optimizeConstEnums', 'optimizeConstEnums' remains unused.\nWithin directory hierarchy 'opts > rewriteImportExtensions', The 'rewriteImportExtensions' section hasn't been filled with any content.\nWithin directory hierarchy 'opts \u2192 rewriteImportExtensions-createImportExpressions', 'rewriteImportExtensions-createImportExpressions' has yet to be populated.\nBack to the top level.\n"}