resume-schema
Advanced tools
Comparing version 0.2.0 to 0.2.1
{ | ||
"name": "resume-schema", | ||
"version": "0.2.0", | ||
"version": "0.2.1", | ||
"description": "JSON Resume Schema", | ||
@@ -5,0 +5,0 @@ "main": "validator.js", |
@@ -10,6 +10,2 @@ # JSON Resume Schema | ||
### Gitter | ||
Everyone working on the early stages of the project should join our gitter channel [gitter.im/jsonresume/public](https://gitter.im/jsonresume/public). | ||
### Getting started | ||
@@ -24,12 +20,16 @@ | ||
```js | ||
var resumeSchema = require('resume-schema'); | ||
resumeSchema.validate({ name: "Thomas" }, function (err, report) { | ||
if (err) { | ||
console.error('The resume was invalid:', err); | ||
return; | ||
const resumeSchema = require("resume-schema"); | ||
resumeSchema.validate( | ||
{ name: "Thomas" }, | ||
function (err, report) { | ||
if (err) { | ||
console.error("The resume was invalid:", err); | ||
return; | ||
} | ||
console.log("Resume validated successfully:", report); | ||
}, | ||
function (err) { | ||
console.error("The resume was invalid:", err); | ||
} | ||
console.log('Resume validated successfully:', report); | ||
}, function(err) { | ||
console.error('The resume was invalid:', err); | ||
}); | ||
); | ||
``` | ||
@@ -40,5 +40,5 @@ | ||
```js | ||
var fs = require('fs'); | ||
var resumeSchema = require('resume-schema'); | ||
var resumeObject = JSON.parse(fs.readFileSync('resume.json', 'utf8')); | ||
var fs = require("fs"); | ||
var resumeSchema = require("resume-schema"); | ||
var resumeObject = JSON.parse(fs.readFileSync("resume.json", "utf8")); | ||
resumeSchema.validate(resumeObject); | ||
@@ -50,12 +50,8 @@ ``` | ||
```js | ||
require('resume-schema').schema; | ||
require("resume-schema").schema; | ||
``` | ||
### People | ||
* Julian Shapiro for early prototype revisions | ||
### Contribute | ||
We encourage anyone who's interested in participating in the formation of this standard, to join us on Gitter, and/or to join the discussions [here on GitHub](https://github.com/jsonresume/resume-schema/issues). Also feel free to fork this project and submit new ideas to add to the JSON Resume Schema standard. To make sure all formatting is kept in check, please install the [EditorConfig plugin](http://editorconfig.org/) for your editor of choice. | ||
We encourage anyone who's interested in participating in the formation of this standard to join the discussions [here on GitHub](https://github.com/jsonresume/resume-schema/issues). Also feel free to fork this project and submit new ideas to add to the JSON Resume Schema standard. To make sure all formatting is kept in check, please install the [EditorConfig plugin](http://editorconfig.org/) for your editor of choice. | ||
@@ -73,15 +69,15 @@ ### Versioning | ||
### Research | ||
We use automatic semver system. | ||
- [A more professional recruitment process with structured data](/research/A%20more%20professional%20recruitment%20process%20with%20structured%20CV%20data.pdf). | ||
Pull requests titles should be formatted as such | ||
### Proposals to reinvestigate | ||
``` | ||
"fix: added something" - will bump the patch version | ||
"feat: added something" - will bump the minor version | ||
"perf: added something" - will bump the major version | ||
``` | ||
* [#69 - Standard format for phone numbers](https://github.com/jsonresume/resume-schema/issues/69) | ||
* [#44 - Person-Job Fit ](https://github.com/jsonresume/resume-schema/issues/44) | ||
* [#12 - geotag location in work ](https://github.com/jsonresume/resume-schema/issues/12) | ||
* [#51 - Support multiple positions within one job](https://github.com/jsonresume/resume-schema/issues/51) | ||
### Other resume standards | ||
### Other resume standards | ||
* [HR-XML](https://schemas.liquid-technologies.com/HR-XML/2007-04-15/) | ||
* [Europass](http://europass.cedefop.europa.eu/about-europass) | ||
- [HR-XML](https://schemas.liquid-technologies.com/HR-XML/2007-04-15/) | ||
- [Europass](http://europass.cedefop.europa.eu/about-europass) |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
30866
79