Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Missing deprecation warning for deprecated tokenName property

See original GitHub issue

The error: Error: Missing configuration keys: [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ] It happens after checking for missing config keys.

Part of the stack trace:

Error: Missing configuration keys: [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,  ]
    at checkForMissingConfigurationKeys (/home/mathieu/WebstormProjects/jhipster-core/lib/dsl/self_checks/parsing_system_checker.js:74:11)
    at checkConfigKeys (/home/mathieu/WebstormProjects/jhipster-core/lib/dsl/self_checks/parsing_system_checker.js:57:3)
    at Object.<anonymous> (/home/mathieu/WebstormProjects/jhipster-core/lib/dsl/validator.js:27:8885)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Module.replacementCompile (/home/mathieu/WebstormProjects/jhipster-core/node_modules/append-transform/index.js:58:13)
    at Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Object.<anonymous> (/home/mathieu/WebstormProjects/jhipster-core/node_modules/append-transform/index.js:62:4)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/home/mathieu/WebstormProjects/jhipster-core/lib/dsl/api.js:17:301)

I can provide the entire stack trace if you want. I’ll try to find why in the meantime

Issue Analytics

State:
Created 4 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

bd82commented, Sep 28, 2019

Hmm yeah A getter that acts as an alias (to avoid actual duplication) would be best. Next major version the getter can be modified to throw an descriptive error.

1reaction

bd82commented, Sep 28, 2019

I am thinking about adding a getter to X.tokenName that will throw a descriptive error message. That seems that it would reduce 95% of the problem with 5% of the effort.

What do you think @MathieuAA ?