-
Notifications
You must be signed in to change notification settings - Fork 64
Issues: whitlockjc/json-refs
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Lodash versions <4.17.21 have security vulnerabilities
#193
opened Jun 24, 2021 by
danbEbsco
updated Apr 10, 2023
JsonRefsOptions location set to relative path containing more than 1 level generates invalid fqURI
#189
opened Mar 6, 2021 by
gilmcquillan
updated Mar 6, 2021
Super deep references found but not resolved
#177
opened Feb 28, 2020 by
kenisteward
updated Jan 20, 2021
Resolution does not work when first level properties contain circular references.
#180
opened Jun 14, 2020 by
tjainesri
updated Jun 16, 2020
Filter 'relative' does not behave as expected
#154
opened Mar 5, 2019 by
saguinav
updated Mar 11, 2019
Cannot find a way to use a custom ref resolver
#150
opened Dec 12, 2018 by
alasdairhurst
updated Dec 13, 2018
Unexpected "Invalid string length" error
#148
opened Nov 12, 2018 by
whitlockjc
updated Nov 12, 2018
Add support for a deep copy of all duplicate references
#147
opened Nov 2, 2018 by
J3tto
updated Nov 2, 2018
TypeScript definitions for
resolveRefsAt
are still invalid
#146
opened Oct 4, 2018 by
oleg-codaio
updated Oct 4, 2018
Dependency on uri-js threatens node 0.8 - node 4.x compatibility
#132
opened Apr 13, 2018 by
ethanherbertson
updated Apr 13, 2018
Update documentation for non-JSON support
#123
opened Aug 25, 2017 by
whitlockjc
updated Aug 25, 2017
Support URI Resolution Scope Alteration compatible with JSON Schema
#3
opened Nov 20, 2014 by
ippeiukai
updated Feb 13, 2016
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.