Welcome to Skinfer’s documentation!¶
Contents:
Skinfer - tool for working with JSON schemas¶
Simple tool to infer and/or merge JSON schemas
- Free software: BSD license
- Documentation: https://skinfer.readthedocs.org.
Features¶
- Generating schema in JSON Schema draft 4 format
- Inferring schema from multiple samples
- Merging schemas - nice for generating schema in Map-Reduce fashion or updating an old schema with new data
Example of using skinfer to generate a schema from a list of samples:
$ cat samples.jsonl
{"name": "Claudio", "age": 29}
{"name": "Roberto", "surname": "Gomez", "age": 72}
$ skinfer --jsonlines samples.jsonl
{
"$schema": "http://json-schema.org/draft-04/schema",
"required": [
"age",
"name"
],
"type": "object",
"properties": {
"age": {
"type": "number"
},
"surname": {
"type": "string"
},
"name": {
"type": "string"
}
}
}
Install with:
$ pip install skinfer
Or, if you don’t have pip
, you can still install it with:
$ easy_install skinfer
Usage¶
Infering schemas from multiple samples¶
Use the skinfer script to generate a schema from a list of samples:
$ skinfer --help
usage: skinfer [-h] [--jsonlines] SAMPLE [SAMPLE ...]
Generates a JSON schema based on samples
positional arguments:
SAMPLE JSON data sample files
optional arguments:
-h, --help show this help message and exit
--jsonlines Assume samples are in JSON lines format
You can also infer the schema programatically:
>>> import skinfer, json
>>> sample1 = {'name': 'Claudio'}
>>> sample2 = {'name': 'Roberto', 'surname': 'Salazar'}
>>> schema = skinfer.infer_schema([sample1, sample2])
>>> import pprint
>>> pprint.pprint(schema)
{'$schema': u'http://json-schema.org/draft-04/schema',
u'properties': {'name': {'type': 'string'}, 'surname': {'type': 'string'}},
u'required': ['name'],
u'type': u'object'}
Using the API, you can also generate a schema for only one sample:
>>> skinfer.generate_schema({"name": "Claudio", "surname": "Salazar"})
{'$schema': u'http://json-schema.org/draft-04/schema',
'properties': {'name': {'type': 'string'}, 'surname': {'type': 'string'}},
'required': ['surname', 'name'],
'type': 'object'}
Merging existing JSON Schemas¶
Use schema_merger to merge a list of JSON schemas into one JSON schema that represents the common properties:
$ schema_merger --help
usage: schema_merger [-h] [-o OUTPUT] schemas [schemas ...]
Merges given JSON Schemas, inferring the required properties
positional arguments:
schemas List of JSON schema files to merge
optional arguments:
-h, --help show this help message and exit
-o OUTPUT Write JSON schema to this file
You can also merge the schema programatically:
>>> import skinfer
>>> any_object = {'type': 'object'}
>>> requires_name = {'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string'}}}
>>> merged_schema = skinfer.merge_schema(any_object, requires_name)
>>> import pprint
>>> pprint.pprint(merged_schema)
{u'properties': {'name': {'type': 'string'}}, u'type': u'object'}
Contributing¶
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report Bugs¶
Report bugs at https://github.com/scrapinghub/skinfer/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Fix Bugs¶
Look through the GitHub issues for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Implement Features¶
Look through the GitHub issues for features. Anything tagged with “feature” is open to whoever wants to implement it.
Write Documentation¶
JSON Schema Merger could always use more documentation, whether as part of the official JSON Schema Merger docs, in docstrings, or even on the web in blog posts, articles, and such.
Submit Feedback¶
The best way to send feedback is to file an issue at https://github.com/scrapinghub/skinfer/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Get Started!¶
Ready to contribute? Here’s how to set up skinfer for local development.
Fork the skinfer repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/skinfer.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv skinfer $ cd skinfer/ $ python setup.py develop
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
$ flake8 skinfer tests $ python setup.py test $ tox
To get flake8 and tox, just pip install them into your virtualenv.
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
- The pull request should work for Python 2.7 and for PyPy. Check https://travis-ci.org/scrapinghub/skinfer/pull_requests and make sure that the tests pass for all supported Python versions.
Credits¶
Development Lead¶
- Scrapinghub <info@scrapinghub.com>
Contributors¶
None yet. Why not be the first?
History¶
0.2.0 (2015-10-10)¶
- Renamed entry-point script schema_inferer -> skinfer
- Added json_validator
- Dropped Python 2.6 support
- Added more tests
0.1.2 (2015-08-04)¶
- Bugfix: removed buggy -o argument
- Automated PyPI release via Travis
0.1.1 (2015-05-01)¶
- Support more complex string-type schemas
- Attempt to infer JSON lines format instead of just failing
- API cleanup: no need for long imports anymore
- Updated documentation, added docstrings
- Fixed merging schema for arrays with tuple vs list validation
- Fixed compatibility issues with Python 2.6
- Improved test coverage, added end-to-end tests
0.1.0 (2015-03-03)¶
- First release on PyPI.