marigold-dev / marigold-dev/training-nft-1
Contract compilation issue
Nobody has claimed this yet.
- Dominant language
- LigoLANG
- Stars
- 11
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Getting the following error trying to compile the contract with
TAQ_LIGO_IMAGE=ligolang/ligo:1.1.0 taq compile nft.jsligo
```
=== Error messages for nft.jsligo ===
[
{
"status": "error",
"stage": "typer",
"content": {
"message": "Type \"ret\" declared in signature but not found.",
"location": [
"File",
{
"start": {
"byte": {
"pos_fname": "/Users/soylentextra/Documents/repos/smart-contracts/nft-marketplace/.ligo/source/i/ligo__s__fa__1.0.9__ffffffff/lib/fa2/nft/nft.impl.jsligo",
"pos_lnum": 11,
"pos_bol": 0,
"pos_cnum": 7
},
"point_num": 1453,
"point_bol": 1446
},
"stop": {
"byte": {
"pos_fname": "/Users/soylentextra/Documents/repos/smart-contracts/nft-marketplace/.ligo/source/i/ligo__s__fa__1.0.9__ffffffff/lib/fa2/nft/nft.impl.jsligo",
"pos_lnum": 239,
"pos_bol": 0,
"pos_cnum": 1
},
"point_num": 9212,
"point_bol": 9211
}
}
]
}
}
]
===
┌────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Source │ Artifact │
├────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ nft.jsligo │ No contract modules found in "nft.jsligo". │
│ │ If your contract is defined within a namespace, please ensure that it is exported from the contract file." │
└────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with `TAQ_LIGO_IMAGE=ligolang/ligo:1.1.0 taq compile nft.jsligo` and inspect the reported `nft.impl.jsligo` location under `.ligo/source`. Trace why the `ret` type in the signature is not found and why no contract module is detected; done means the contract compiles and the module is recognized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100