Ben/multi org

[blugavere]

Add recursive folder structure reading & labeling support.

#82

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 8c05da2:

Sandbox	Source
demo	Configuration

[bourdakos1]

I think _category_ should be excluded by GlobExcludeDefault above, which excludes anything that starts with an underscore?

[blugavere]

doesn't appear to work

[bourdakos1]

Ah yea looks like it doesn't ignore json files with _

  // Ignore files starting with _
  '**/_*.{js,jsx,ts,tsx,md,mdx}',

  // Ignore folders starting with _ (including folder content)
  '**/_*/**',

  // Ignore tests
  '**/*.test.{js,jsx,ts,tsx}',
  '**/__tests__/**',

[bourdakos1]

maybe try something like this then:

[...GlobExcludeDefault, '**/_*.{json,yaml,yml}']

[bourdakos1]

Can we rename __test__ to __fixtures__?

[bourdakos1]

Looking good, I still need to look over the category tree stuff

[bourdakos1]

This makes me a little uncomfortable having the existence of source being tied to the existence of api.info. Maybe we should just use items[0].source and items[0].sourceDirName? However, with hardcoding zero index we have to think if there is ever a case were items is an empty array? Maybe an empty directory, or spec that wouldn't generate any pages, etc... We should probably have a case that skips creating the category/subitems if we don't have the right info

[blugavere]

If there is ever a case were items is an empty array?

I don't think so but can mull on it.

The current implementation (for all of multi-spec) relies on the folder structure being generated from OpenAPI Specs (& these lines are only hit if there are > 1 spec files).

Arbitrary markdown files aren't supported. Introductions are automatically generated from the info.description field so in all cases a section is only created for an openapi spec. Here we're ignoring the auto-generated markdown file from being used to select the sidebar label after being grouped by source.

The fn input items[] is a flattened array of ["auto-generated markdown for spec a", "openapi path for spec a"]. The .find fn is getting not the zero index, but the first element in the group which is non-markdown & has the openapi spec info. If falsy, defaults to filename.

[bourdakos1]

Looks good! We can investigate potential issues with an empty array of pages later