fix(types): make RequestInit properties assignable

[NMinhNguyen]

Fixes #1445

[codecov-commenter]

Codecov Report

Merging #1446 (36cf3c9) into main (5478cdd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1446   +/-   ##
=======================================
  Coverage   94.37%   94.37%           
=======================================
  Files          49       49           
  Lines        4231     4231           
=======================================
  Hits         3993     3993           
  Misses        238      238           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5478cdd...36cf3c9. Read the comment docs.

[mcollina]

Can you fix the PR title? the linter is complaining?

[NMinhNguyen]

I’m not sure why that is - the error message is complaining about the old title:

No release type found in pull request title "Make sure RequestInit properties are assignable".

I’ll try changing it and back again

[NMinhNguyen]

I think all the checks are passing?

[KhafraDev]

All the checks here show as successful (which is where I got confused as well), but the action shows that it's failing:

Error: No release type found in pull request title "Make sure `RequestInit` properties are assignable". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

I re-ran it and now it passed. 🤷

[mcollina]

lgtm

[NMinhNguyen]

Thanks for the prompt reviews and merging! What's the release cadence by the way? Are you looking to merge a few more PRs before publishing a new version?