Enhance header filtering in getHeadersApplicableToAllResources function to exclude falsy values

[ivanvakulov]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

This pull request includes a small change to the src/utils/headers.ts file. The change ensures that only headers with non-falsy values are included in the result.

• src/utils/headers.ts: Added a filter to remove headers with falsy values in the getHeadersApplicableToAllResources function.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)

[vejja]

@ivanvakulov Thank you very much for this PR
Would you be able to add unit tests to make sure that the functionality works as expected, including for falsy values such as undefined?
I think they probably belong to /test/perRoute
Just want to make sure that setting false somewhere in the hierarchy of route rules won't impact another sub route somewhere

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
security	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 19, 2024 7:42pm

[ivanvakulov]

@vejja Thank you for the review. I've added new tests for publicAssets to ensure there are no empty headers and that headers are correctly set according to the routeRules.

[vejja]

@Baroshem LGTM

[Baroshem]

Amazing work @ivanvakulov

Thanks @vejja for checking it!