Open grijeshsaini opened 6 months ago
π @grijeshsaini
π Thanks for opening this pull request! π
Please follow the contributing guidelines. And we use semantic commit messages to streamline the release process.
Examples of commit messages with semantic prefixes:
fix: don't overwrite prevent_default if default wasn't prevented
feat: add graph.scale() method
docs: graph.getShortestPath is now available
Things that will help get your PR across the finish line:
npm run lint
locally to catch formatting errors earlier.We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.
Attention: 4 lines
in your changes are missing coverage. Please review.
Comparison is base (
b751cbf
) 62.93% compared to head (7aee57e
) 63.10%. Report is 4 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
src/embed-webfonts.ts | 0.00% | 4 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
--
In scenarios where elements contain multiple URLs, including both internal and public links, there arises a need to supply distinct RequestInit configurations for various fetch requests.
Presently, the limitation lies in the fact that we can only provide a single fetchRequestInit, and this configuration is globally applied to all fetch calls for that element.
This proposed feature aims to enhance flexibility by enabling the provision of RequestInit configurations tailored to individual fetch requests based on their respective URLs. This enhancement ensures more granular control over the customization of fetch request behaviors, facilitating better handling of internal and public URLs.
Self Check before Merge