fix: default value of the singleFile is changed#757
fix: default value of the singleFile is changed#757asyncapi-bot merged 2 commits intoasyncapi:masterfrom
Conversation
|
|
Hey, you did an great job, but what i think is -> changing the default to a string ("false") isn’t the right fix. "default": falseThe issue is in the generator not handling false defaults, not the template. "const": false Check these lines and update to "const": "false" -> "const": false Just sharing so the PR stays correct. |
|
okay, can you explain me where the generator is not handling the default false, and also i think params should be false not "false". there is no need to handle for both cases but let's see what maintainers say |
|
Yeah, that makes sense, ideally singleFile should always be a boolean... const singleFile = (params?.singleFile === true || params?.singleFile == 'true');So boolean true and string "true" are both supported.... let’s wait and see what the maintainers say, they might want to standardize this one way or the other |
|
folks did you see my comment in issue you linked? |
|
@batchu5 for some reason this PR is hanging in infinite loop. I'll see if closing and reopening will fix it.
|
|
|
/rtm |
|
🎉 This PR is included in version 3.5.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |




Description
In generator if we give the params as -p single=false eventually, it is converting into single = 'false' , that is changed into singleFile='false', so changing the default value from false to 'false' in package.json results in string and css and js files are generated
Fixes #744