fix: installation breaks due to lefthook in postinstall

[Shahroz16]

No description provided.

[github-actions]

Pull request title looks good 👍!

If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.1. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy!

This pull request title should be in this format:

<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:

<type>!: short description of breaking change

where <type> is one of the following:

• feat: - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project.

• fix: - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project.

• docs: - This pull request is making documentation changes, only.

• refactor: - A change was made that doesn't fix a bug or add a feature.

• test: - Adds missing tests or fixes broken tests.

• style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

• perf: - Changes improve performance of the code.

• build: - Changes to the build system (maven, npm, gulp, etc)

• ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

• chore: - Other changes to project that don't modify source code or test files.

• revert: - Reverts a previous commit that was made.

Examples:

feat: edit profile photo
refactor!: remove deprecated v1 endpoints
build: update npm dependencies
style: run formatter 

Need more examples? Want to learn more about this format? Check out the official docs.

Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[mrehan27]

Just one questions, looks good overall 👍🏻

[levibostian]

Why was this changed to false?

[Shahroz16]

Because it's breaking the build, this also runs on Sample App which has more than 60 warnings.

On a side note, why do we fail or warning? we don't on any other SDK? we only fail on errors. Why do we need to fail on warning as they at times very opinionated?

[levibostian]

This config change in this PR is a good change for the short-term. Especially because...

also runs on Sample App which has more than 60 warnings.

For a long-term solution, I prefer to make warnings be treated as errors and if there is a rule that the team feels is not needed, we ignore that rule.

I prefer this method because I don't see much value in lint warnings if they are not treated as errors. If lint warnings should not throw an error on the CI server and therefore be allowed to be merged into main, why not instead add that lint rule to the lint ignore list? To me, those 2 things are the same thing: we either follow a lint rule, or we don't. Lint warnings, IMO, are a 🤷🏻 if we follow the rule or not.