docs(ng-icons): update responseType in custom SVG loader example #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the documentation for the
provideNgIconLoader
usage example. The current documentation does not specify theresponseType
in the HTTP request, which leads to a type mismatch error as theHttpClient.get
method defaults to returning anObservable<Object>
.Changes made:
{ responseType: 'text' }
as the second argument to thehttp.get
method to ensure the response is treated as a plain text string.This modification ensures that when fetching custom SVG icons, the response is handled as an
Observable<string>
, which aligns with the expected return type for theprovideNgIconLoader
function. The update should prevent type mismatch errors and clarify the correct usage for future developers.By correcting this example, developers will have a smoother experience when implementing custom SVG icon loaders using the
ng-icons
library.