A simplified way to generate masive mock data based on a schema, you can use the awesome fake/random data generators like (FakerJs, ChanceJs, CasualJs and RandExpJs)
This version is covered by your current version range and after updating it in your project the build failed.
As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/danibram/mocker-data-generator/builds/238139851?utm_source=github_status&utm_medium=notification)
- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/danibram/mocker-data-generator/build/118)
Release Notesv5.4.0
[new-rule-option] ban new options format: allows to specify an optional explanation message for function bans, banning nested methods and using a wildcard for object of a method ban (#2547)
[new-rule-option] no-duplicate-variable adds check-parameters option to check if variable has the same name as a parameter (#2597)
[bugfix] no-unsafe-any: Don't mark declare global {} as an unsafe any. (#2839)
[bugfix] indent now checks indentation of expressions inside template strings (#2826)
[enhancement] --project (or -p) enables rules that require the type checker. --type-check only checks for errors before linting is no longer required (#2773)
[enhancement] deprecation: error message includes deprecation text if available (#2748)
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
danibram
commented
7 years ago
Version 5.4.0 of tslint just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/danibram/mocker-data-generator/builds/238139851?utm_source=github_status&utm_medium=notification) - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/danibram/mocker-data-generator/build/118)Release Notes
v5.4.0switch-final-break(#2804)use-default-type-parameter(#2253)binary-expression-operand-order(#2805)bannew options format: allows to specify an optional explanation message for function bans, banning nested methods and using a wildcard for object of a method ban (#2547)no-duplicate-variableaddscheck-parametersoption to check if variable has the same name as a parameter (#2597)curly: "as-needed" option (#2842)no-unbound-methodadd option"ignore-static"(#2751)strict-boolean-expressionsaddsallow-boolean-or-undefined(#2820)object-literal-shorthandcan fix longhand methods (#2558)prefer-object-spreadallows constructor, function and method calls and more as first argument toObject.assign(#2828)no-unbound-methodwalker skips past the parent if it is a cast or parenthesized expression (#2838)object-literal-shorthand: fixed suggestion for generator functions (#2558)no-unused-variablerule on Windows (#2819)tslint --projectifallowJsis set in tsconfig.json (#2823)alignwith option"members": check members of class expressions; don't check semicolons in classes (#2668)no-inferred-empty-object-type: fix stack overflow (#2762)semicolon: don't warn about unnecesary semicolon when it is actually needed, e.g. when followed by type assertion or template string (#2655)space-before-function-paren: Ignore async arrow function with no parentheses (#2833)no-unsafe-any: Don't fail oncontinue label;(#2830)no-unbound-method: Allow unbound method to be used as a condition (#2834)no-unsafe-any: Allow to switch on a value of typeany(#2836)no-unsafe-any: Don't markdeclare global {}as an unsafe any. (#2839)indentnow checks indentation of expressions inside template strings (#2826)--project(or-p) enables rules that require the type checker.--type-checkonly checks for errors before linting is no longer required (#2773)deprecation: error message includes deprecation text if available (#2748)cyclomatic-complexity: Don't count empty switch case(#2743)strict-boolean-expressions: Allowany, andtrueandfalseliteral types (#2758)no-floating-promises: Allow 'promise.catch()' (#2774)comment-formatno longer excludes comments with triple slash from linting except/// <reference path="..."/>(#2616)prefer-object-spread: lint more locations where return value is used. (#2828)semicolon: option"never"is now spec compliant (#2655)object-literal-shorthandhandles async functions correctly (#2558)--testCLI option: allow passing path to tslint.json (#2784)strict-type-predicates: warn if strictNullChecks is not enabled (#2786)Thanks to our contributors!
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: