nspcc-dev/neo-go

Create contract manifest during compilation

Open

#1,038 opened on Jun 9, 2020

View on GitHubContributor guide
 (8 comments) (0 reactions) (0 assignees)Go (108 forks)auto 404
I1S2U4compilerdiscussionhelp wanted

Repository metrics

Stars
 (132 stars)
PR merge metrics
 (PR metrics pending)

Description

While some of the contract features cannot be determined from the contract source (e.g. IsPayable) most of them can. Method and Event descriptions should be generated automatically. I think it is also worth supporting Permissions/Groups (via magic comments?), so that manifest can be completely generated from source.

Contributor guide

Research direction
Explore the neo go compiler source code to understand how contract features like IsPayable are currently determined and where method/event descriptions are generated. Look for existing magic comment usage and identify where to add automatic manifest generation.
Tech stack
go
Domain
blockchain
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoNeo blockchain basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55