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

fix for frictionlessdata/specs/issues/645 #646

Merged
merged 1 commit into from Nov 28, 2019

Conversation

@iSnow
Copy link
Contributor

iSnow commented Oct 31, 2019

Added the proposed fix to the YAML sources

@rufuspollock

This comment has been minimized.

Copy link
Contributor

rufuspollock commented Nov 2, 2019

atm this is looking like a wontfix given discussion in #645

@roll roll added this to Specifications in General Nov 4, 2019
@iSnow

This comment has been minimized.

Copy link
Contributor Author

iSnow commented Nov 19, 2019

Given that the current state breaks validating via general-purpose schema validators like https://www.jsonschemavalidator.net/ , and no one has come up with a drawback of allowing either objects or url-or-path references, I'd like to ask again whether this could be merged.

@rufuspollock rufuspollock merged commit da73fa0 into frictionlessdata:master Nov 28, 2019
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
General automation moved this from Specifications to Done Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
General
  
Done
3 participants
You can’t perform that action at this time.