Skip to content
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

Multiple feats #186

Merged
merged 7 commits into from
May 9, 2024
Merged

Multiple feats #186

merged 7 commits into from
May 9, 2024

Conversation

AlexMCon
Copy link
Collaborator

@AlexMCon AlexMCon commented May 9, 2024

Pull Request Template

Description

Please include a summary of the change and which issue is fixed. Additionally, please provide context necessary to understand why these changes were made and how they address the issue.

Fixes # (issue reference)

Type of Change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

Before submitting your pull request, please review the following checklist:

  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • Any dependent changes have been merged and published in downstream modules.

Additional Information

Any additional information, configuration, or data that might be necessary to reproduce the issue or test the feature.

1. Added issue link in first commit message
2. Removed version, datacap applicant and project id from issue parsing
3. Added allowance vs allocation amount check on trigger (review), propose and approve steps
Copy link
Collaborator

@clriesco clriesco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for testing. See attached comments before going to prod

new_allocation_amount: Option<String>,
) -> Result<(), LDNError> {
let blockchain = BlockchainData::new();
match blockchain.get_allowance_for_address("f24siazyti3akorqyvi33rvlq3i73j23rwohdamuy").await {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leave this as it is just for testing purposes. We need to remove it when tagging into prod

},
};

println!("===============================");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove prints on tagging

match compare_allowance_and_allocation(&allowance, new_allocation_amount) {
Some(result) => {
if result {
println!("Allowance is sufficient.");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove prints on tagging

@AlexMCon AlexMCon merged commit 89c294b into main May 9, 2024
1 check passed
@kacperzuk-neti kacperzuk-neti deleted the multiple-feats branch June 6, 2024 12:32
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.

None yet

2 participants