We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
after a change from 2.1.0 to 2.2.1 we found out that somehow a breaking change occured. We have this object in our config.json (kraken)
"cookies": { "expires": 0, "secure": false, "signed": true }
In 2.1.0 after using: config.get('cookies') we received: { expires: 0, secure: false, signed: true }
config.get('cookies')
{ expires: 0, secure: false, signed: true }
but in 2.2.1 we got: { expires: '0', secure: false, signed: true }
{ expires: '0', secure: false, signed: true }
Please take a look at this issue, unfortunately kraken-js is taking all non-breaking changes from confit and it has impact on our project.
The text was updated successfully, but these errors were encountered:
Confirmed that it breaks expressjs setting like 'json spaces' giving this kind of json response output du to "0" in place of 0:
{ 0"splitDiscussionsByLang": true, 0"hideFooter": false, 0"maxSlidePerChapter": 3, 0"maxSlidePerChapterBattle": 2, 0"maxTyposForSlides": 2, 0"maxShots": 3, 0"maxStars": 2000, 0"badgesLimits": { 00"battle": [ 0003, 00010, 00025, 00050 00], 00"coach": [
Sorry, something went wrong.
No branches or pull requests
Hi,
after a change from 2.1.0 to 2.2.1 we found out that somehow a breaking change occured.
We have this object in our config.json (kraken)
In 2.1.0 after using:
config.get('cookies')
we received:
{ expires: 0, secure: false, signed: true }
but in 2.2.1 we got:
{ expires: '0', secure: false, signed: true }
Please take a look at this issue, unfortunately kraken-js is taking all non-breaking changes from confit and it has impact on our project.
The text was updated successfully, but these errors were encountered: