Skip to content

Fix ci issues due to x/mint#129

Merged
philipsu522 merged 3 commits intomasterfrom
fix-mint-ci
Jul 18, 2022
Merged

Fix ci issues due to x/mint#129
philipsu522 merged 3 commits intomasterfrom
fix-mint-ci

Conversation

@philipsu522
Copy link
Contributor

@philipsu522 philipsu522 commented Jul 18, 2022

#113 actually created lint errors. Remove these tests (osmosis doesn't have it either: https://sourcegraph.com/github.com/osmosis-labs/osmosis@2d0ef14/-/tree/x/mint/client)

@philipsu522 philipsu522 merged commit c9f2b03 into master Jul 18, 2022
philipsu522 added a commit that referenced this pull request Jul 19, 2022
* Rm unneeded files

* run gofumpt

* Ignore err check
alg747 pushed a commit to UXDProtocol/sei-chain that referenced this pull request Jul 20, 2022
* Rm unneeded files

* run gofumpt

* Ignore err check
masih pushed a commit that referenced this pull request Sep 29, 2025
…129)

## Describe your changes and provide context
This adds the conservative fallback behavior for the JQ selectors when
processing a contract reference. Because we are in a contract reference,
we don't necessarily know that the JSON body is proper, therefore if a
JQ selector doesn't have a match, we have to conservatively assume that
it is because the JSON incorrectly doesn't include that field instead of
the dependency not being necessary. As a result, these JQ selectors will
modify the identifier template to be "*" (aka the conservative value for
that resource) in the case that the selector doesn't have a match

## Testing performed to validate your change
Updated unit tests to verify this behavior and also to test that we
properly discard JQ selectors when NOT in a contract reference.
masih pushed a commit that referenced this pull request Sep 30, 2025
…129)

## Describe your changes and provide context
This adds the conservative fallback behavior for the JQ selectors when
processing a contract reference. Because we are in a contract reference,
we don't necessarily know that the JSON body is proper, therefore if a
JQ selector doesn't have a match, we have to conservatively assume that
it is because the JSON incorrectly doesn't include that field instead of
the dependency not being necessary. As a result, these JQ selectors will
modify the identifier template to be "*" (aka the conservative value for
that resource) in the case that the selector doesn't have a match

## Testing performed to validate your change
Updated unit tests to verify this behavior and also to test that we
properly discard JQ selectors when NOT in a contract reference.
@masih masih deleted the fix-mint-ci branch October 31, 2025 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants