Skip to content

Remove boolean options fallback#150

Merged
bilelmoussaoui merged 1 commit into
flatpak:masterfrom
tytan652:no_fallback_for_boolean_options
Aug 25, 2023
Merged

Remove boolean options fallback#150
bilelmoussaoui merged 1 commit into
flatpak:masterfrom
tytan652:no_fallback_for_boolean_options

Conversation

@tytan652

Copy link
Copy Markdown
Contributor

While unnecessary since all of them have a default value
Having build-bundle set to false was is fact turning it to true through the fallback

@bilelmoussaoui

Copy link
Copy Markdown
Member

oh, good catch

@bilelmoussaoui

Copy link
Copy Markdown
Member

i wonder why the ncc build diff is so huge this time

@tytan652

tytan652 commented Aug 19, 2023

Copy link
Copy Markdown
Contributor Author

i wonder why the ncc build diff is so huge this time

I don't know, I just installed ncc and done the command. Should I have done another npm/yarn command before ?

@tytan652 tytan652 force-pushed the no_fallback_for_boolean_options branch from 66764d4 to bc60dce Compare August 19, 2023 22:37
@tytan652

tytan652 commented Aug 19, 2023

Copy link
Copy Markdown
Contributor Author

I think I found the issue, I think need to use yarn install --pure-lockfile

Edit: I'm really not used to JS development.

While unnecessary since all of them have a default value
Having build-bundle set to false was is fact turning it to true through
the fallback
@tytan652 tytan652 force-pushed the no_fallback_for_boolean_options branch from bc60dce to f1abcd3 Compare August 19, 2023 22:43
@tytan652

Copy link
Copy Markdown
Contributor Author

Dist files should be fixed and good now.

@bilelmoussaoui bilelmoussaoui merged commit b9a7d06 into flatpak:master Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants