You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I'll add a bunch more shortly, im still on holiday 😇
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.
The text was updated successfully, but these errors were encountered:
philsturgeon
changed the title
Making this functionality available to the OAS community
Making better bundle available to the OAS community
Aug 15, 2021
Unnecessary nit pick. If merging changes back upstream they'd be documented there. Otherwise it would be documented here. Come on. If you're about to start a sentence with "nit pick" probably just delete that sentence.
@mnaumanali94 can you get this on somebodies radar as I don't work here anymore? :D
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
Additional context
It would make a lot of people out there very happy to know we're helping.
The text was updated successfully, but these errors were encountered: