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.

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

RefMap Check Should Resolve Ref Fragment #16

Closed
wants to merge 339 commits into from

Conversation

jordanross-wf
Copy link

Issue:

  • RefMap Check Should Resolve Ref Fragment

Solution:

  • Both sync and async ref resolution methods now use a shared helper method that checks refMap for baseUri and resolves fragment if present.

Michael Carter and others added 30 commits April 18, 2018 10:24
EPL-8413 feat(package): update draft4 tests
EPL-8414 feat(package): support JSON Schema draft6
Update Dockerfile to Mirror smithy.yaml
BUILDTOOLS-2329: Update Dockerfile to mirror smithy.yaml
Update .gitignore to new `dart_tool` pub cache
…a into sync_schemas_2

# Conflicts:
#	lib/src/json_schema/json_schema.dart
#	test/unit/vm/json_schema/validation_test.dart
jordanross-wf and others added 28 commits February 24, 2021 09:19
# Conflicts:
#	lib/src/json_schema/json_schema.dart
#	pubspec.yaml
CPRO-358 fix(ref-resolution): Logic changes around remote ref resolution
CPRO-359: chore(package): update spec tests
…chema properly walks the schema now instead of just searching the _refMap
PROC-709 fix(test): fix test cases involving formats
# Conflicts:
#	test/unit/vm/json_schema/validation_test.dart
PROC-727 Ref Storage on Schemas and Path Resolution Changes
PROC-728: Fix Encoding and UTF-16 Spec Tests
@jordanross-wf
Copy link
Author

PR'd to wrong fork, sorry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.