Skip to content

Making better bundle available to the OAS community #27

Open
@philsturgeon

Description

@philsturgeon

Summary

There are infinite issues on countless packages asking for this new and improved bundling, on our repos (which is why we did it) and various APIDevTools repos.

Can we either, document our fork so people know how the new bundling logic works, or merge our changes back into the upstream so everyone has access to it without needing to switch to our fork?

Tasks

  • Document optimized bundling
  • and/or
  • Merge this functionality upstream to APIDevTools/json-schema-ref-parser so we dont need to maintain this fork

Additional context

It would make a lot of people out there very happy to know we're helping.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions