Skip to content

Conversation

@kziemianek
Copy link
Contributor

@kziemianek kziemianek commented Mar 20, 2023

Adds default attribute for constructors and messages.
default attribute is reflected in metadata so consuming services can for example determine which constructor/message should be selected by default.

#1703

@kziemianek
Copy link
Contributor Author

@HCastano i see you are takinkg a 👀 at this PR. A lot checks have failed because of:

fatal: unable to access 'https://gitlab.parity.io/parity/mirrors/ink.git/': Failed to connect to gitlab.parity.io port 443 after 130941 ms: Operation timed out

It seems like a one time issue, do you have permission to retry checks ?

Copy link
Collaborator

@cmichi cmichi left a comment

Choose a reason for hiding this comment

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

Thank you! Can you create the follow-up issues as mentioned in #1703?

Copy link
Contributor

@HCastano HCastano left a comment

Choose a reason for hiding this comment

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

Nice work, thanks!

return_type: ReturnTypeSpec<F>,
/// The message documentation.
docs: Vec<F::String>,
/// If the message is default
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// If the message is default
/// If the message is the default for off-chain consumers (e.g UIs).

pub return_type: ReturnTypeSpec<F>,
/// The deployment handler documentation.
pub docs: Vec<F::String>,
/// If the constructor is default
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// If the constructor is default
/// If the constructor is the default for off-chain consumers (e.g UIs).

@HCastano HCastano changed the title default attribute for constructors and messages Add #[ink(default)] attribute for constructors and messages Apr 12, 2023
@kziemianek
Copy link
Contributor Author

Thank you! Can you create the follow-up issues as mentioned in #1703?

Yes, I was waiting for approval before moving to downstream projects.

@HCastano HCastano merged commit b4fff41 into use-ink:master Apr 15, 2023
@cmichi cmichi mentioned this pull request Apr 20, 2023
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