Skip to content

Conversation

@daeMOn63
Copy link
Contributor

@daeMOn63 daeMOn63 commented Nov 3, 2021

No description provided.

@daeMOn63 daeMOn63 changed the title Upgrade to cosmwasm 1.0.0. beta [capricorn] Upgrade to cosmwasm 1.0.0. beta Nov 3, 2021
@daeMOn63 daeMOn63 requested a review from ejfitzgerald January 11, 2022 08:19
Copy link
Collaborator

@ejfitzgerald ejfitzgerald left a comment

Choose a reason for hiding this comment

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

Is it possible to remove fetch/bridge.wasm and then just build it and attach to part of the release like I have done in: https://github.com/fetchai/contract-reconciliation. Think that is a nicer way to do things

out_dir.push("schema");
create_dir_all(&out_dir).unwrap();
remove_schemas(&out_dir).unwrap();
/*
Copy link
Collaborator

Choose a reason for hiding this comment

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

Will add an item on to the backlog to add this back in at some point

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added back, that wasn't too hard :)

Some(_) => true,
None => false,
}
store.get(&swap_id.to_be_bytes()).is_some()
Copy link
Collaborator

Choose a reason for hiding this comment

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

👍

Ok(r)
Ok(Response::new()
.add_attributes(attrs)
.add_submessages(rtx.messages))
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is a functional difference right? Did you expect to call .add_message it might not make much of the difference but my recollection is that sub messages are ones where the contract is interested in the response.

Copy link
Contributor Author

@daeMOn63 daeMOn63 Jan 26, 2022

Choose a reason for hiding this comment

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

I think I'm forced to use .add_submessages here because of message signature: pub messages: Vec<SubMsg<T>, Global>. Using .add_message result in the trait bound 'cosmwasm_std::CosmosMsg<_>: From<SubMsg>' is not satisfied

Ok(r)
Ok(Response::new()
.add_attributes(attrs)
.add_submessages(rtx.messages))
Copy link
Collaborator

Choose a reason for hiding this comment

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

See comment above

pub mod msg;
pub mod state;

#[cfg(test)]
Copy link
Collaborator

Choose a reason for hiding this comment

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

😨 - Nice catch!


on: [push, pull_request]
on:
pull_request:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
pull_request:
pull_request:
- master

I seem to remember that you need this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure to see why would we want to restrict actions to run only for PR targeting master? Running for any PR seems fine?

ejfitzgerald
ejfitzgerald previously approved these changes Jan 26, 2022
Copy link
Collaborator

@ejfitzgerald ejfitzgerald left a comment

Choose a reason for hiding this comment

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

Looks good to me - I guess we need to sort out the GH actions though because they don't look like they are working currently

@daeMOn63 daeMOn63 merged commit e9201af into master Jan 27, 2022
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.

3 participants