feat: add amz-content-sha256 extension to docs #3036
+1
−0
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.
Description
@Telroshan Here My PR related to this previous PR on HTMX Extensions. As we discussed there , I hosted the extension on my repository and added it to the Docs as a Community Extension.
This Pull Request adds a new reference to a community extension that addresses use cases where users interact with AWS services that require the SigV4 integrity header, such as in this example. Several AWS services depend on this header, and I encountered this exact issue in my own open-source project that uses HTMX.
Given that others may experience the same issue, I believe this functionality will be beneficial.
Corresponding issue:
This PR on EXtensions
Testing
I added a Test folder into the repository root following the pattern shown in the official htmx-extensions repository.
Checklist
master
for website changes,dev
forsource changes)
approved via an issue
npm run test
) and verified that it succeeded