Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve remote reference processing to avoid duplicates #89

Closed
whitlockjc opened this issue Jun 27, 2016 · 2 comments
Closed

Improve remote reference processing to avoid duplicates #89

whitlockjc opened this issue Jun 27, 2016 · 2 comments

Comments

@whitlockjc
Copy link
Owner

Whenever we process remote documents, we can can end up processing the same document multiple times.
@whitlockjc
Copy link
Owner Author

Keep in mind that processing a document depends on options.subDocPath.

@whitlockjc
Copy link
Owner Author

Would make sense to make this user configurable since there is likely going to be no implementation that works best in all situations.

whitlockjc added a commit that referenced this issue Apr 20, 2017
@whitlockjc
Rewrote resolver for accuracy and efficiency
3debfd5 
The resolver was rewritten to fix numerous bugs and performance issues.
The reason for this is over the years, bug fixes and features have been
added on top of json-refs and its resolver logic has become crufty.  The
new rewrite is clean, does not reinvent the wheel and fixes many bugs.

Fixes: #80, #87, #88, #89, #97, #101, #103
whitlockjc added a commit that referenced this issue Apr 20, 2017
@whitlockjc
Rewrote resolver for accuracy and efficiency
0fc28fa 
The resolver was rewritten to fix numerous bugs and performance issues.
The reason for this is over the years, bug fixes and features have been
added on top of json-refs and its resolver logic has become crufty.  The
new rewrite is clean, does not reinvent the wheel and fixes many bugs.

Fixes: #80, #87, #88, #89, #97, #100, #101, #103
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@whitlockjc