-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: stricter validation of POST json body passed to the textile API. #760
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
n1k0
force-pushed
the
fix/api-post-validation2
branch
2 times, most recently
from
September 19, 2024 05:27
d767b70
to
7c6ce42
Compare
n1k0
force-pushed
the
fix/api-post-validation2
branch
from
September 19, 2024 10:02
c1837c8
to
f4429a0
Compare
@vjousse I'd like a first preliminary look over this patch and know what you think :) |
n1k0
force-pushed
the
fix/api-post-validation2
branch
from
September 19, 2024 11:55
449f4c5
to
6e3204b
Compare
n1k0
force-pushed
the
fix/api-post-validation2
branch
from
September 19, 2024 14:30
ef447ad
to
3638049
Compare
vjousse
reviewed
Sep 19, 2024
vjousse
reviewed
Sep 19, 2024
vjousse
approved these changes
Sep 19, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work and good catch for the Maybe decoding! Tested locally and it works as expected.
n1k0
changed the title
refactor: make POST API request unit-testable.
fix: stricter validation of POST json body passed to the textile API.
Sep 19, 2024
vjousse
pushed a commit
that referenced
this pull request
Sep 25, 2024
[2.3.0](v2.2.0...v2.3.0) (2024-09-25) ### Features * add link to changelog in app footer. ([#748](#748)) ([efe88f5](efe88f5)) * airTransportRatio should depend on durability ([#757](#757)) ([a0761d1](a0761d1)) * displayName in the textile explorer, reordered columns ([#737](#737)) ([65d0ed5](65d0ed5)) ### Bug Fixes * **api:** handle ingredient plane transport in food POST api. ([#769](#769)) ([62587e2](62587e2)) * check db integrity after building it ([#753](#753)) ([5b41ef6](5b41ef6)) * check uniqueness of JSON db primary keys at build time. ([#766](#766)) ([0927954](0927954)) * decode and validate all optionals. ([#764](#764)) ([87a7c6a](87a7c6a)) * encode physicalDurability parameter. ([#751](#751)) ([f6750b8](f6750b8)) * fix github CI python build setup. ([#762](#762)) ([ea2cd9f](ea2cd9f)) * fixed brightway explorer notebook error (wrong key) ([#745](#745)) ([bc436c2](bc436c2)) * in brightway explorer: improve display of compartment categories, if any ([#754](#754)) ([757d5a6](757d5a6)) * stricter validation of POST json body passed to the textile API. ([#760](#760)) ([a85bd8a](a85bd8a)) * **textile:** distribution step had no inland road transports added. ([#761](#761)) ([d789d7d](d789d7d)) * Update export outside of EU probability. ([#765](#765)) ([c3fd9f2](c3fd9f2)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
n1k0
added a commit
that referenced
this pull request
Sep 26, 2024
…#760) There actually wasn't any strict validation performed on some optional parameters passed as a JSON body to POST requests, because we were using the infamous `Json.Decode.maybe` decoder which fallbacks to returning `Nothing` instead of a failure in case the decoded value is invalid.
n1k0
pushed a commit
that referenced
this pull request
Sep 26, 2024
[2.3.0](v2.2.0...v2.3.0) (2024-09-25) ### Features * add link to changelog in app footer. ([#748](#748)) ([efe88f5](efe88f5)) * airTransportRatio should depend on durability ([#757](#757)) ([a0761d1](a0761d1)) * displayName in the textile explorer, reordered columns ([#737](#737)) ([65d0ed5](65d0ed5)) ### Bug Fixes * **api:** handle ingredient plane transport in food POST api. ([#769](#769)) ([62587e2](62587e2)) * check db integrity after building it ([#753](#753)) ([5b41ef6](5b41ef6)) * check uniqueness of JSON db primary keys at build time. ([#766](#766)) ([0927954](0927954)) * decode and validate all optionals. ([#764](#764)) ([87a7c6a](87a7c6a)) * encode physicalDurability parameter. ([#751](#751)) ([f6750b8](f6750b8)) * fix github CI python build setup. ([#762](#762)) ([ea2cd9f](ea2cd9f)) * fixed brightway explorer notebook error (wrong key) ([#745](#745)) ([bc436c2](bc436c2)) * in brightway explorer: improve display of compartment categories, if any ([#754](#754)) ([757d5a6](757d5a6)) * stricter validation of POST json body passed to the textile API. ([#760](#760)) ([a85bd8a](a85bd8a)) * **textile:** distribution step had no inland road transports added. ([#761](#761)) ([d789d7d](d789d7d)) * Update export outside of EU probability. ([#765](#765)) ([c3fd9f2](c3fd9f2)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Funnily enough, while we were thinking there wasn't any validation applied to some input POST parameters in the API, it was in fact our unit test env which was unable to execute these tests, because it didn't have access to the native JSON body to execute the correct assertions. Validation was working in e2e tests just fine… I should probably have spotted that earlier.Edit: There actually wasn't any validation performed on some optional parameters passed as a JSON body to POST requests, because we were using the infamous
Json.Decode.maybe
decoder which fallbacks to returningNothing
instead of a failure in case the decoded value is invalid. This patch leverages Json.Decode.Extra.optionalField instead: