When using `flow-c1`, `dependencies` field in `flow.json` can not be recognized by language server

onflow / flow-cli

The Flow CLI is a command-line interface that provides useful utilities for building Flow applications

https://onflow.org

Apache License 2.0

208 stars 66 forks source link

When using `flow-c1`, `dependencies` field in `flow.json` can not be recognized by language server #1698

Open btspoony opened 1 month ago

btspoony commented 1 month ago

Instructions

Problem

Using flow-c1 the Cadence language server in VSCode cannot recognize the dependencies field in flow.json, so I have to configure another contracts field.

Steps to Reproduce

Switch to flow-c1
Using dependency manager to add some dependencies.

Acceptance Criteria

Let it work

Context

flow-c1 1.21.0-c1.0-preview.32

chasefleming commented 1 month ago

@bthaile @gregsantos I'm not sure how solvable this is until we are completely migrated since different networks are using a different version of Cadence and each CLI version uses one version of the language parser.

jribbink commented 1 month ago

@btspoony for the "source" of the dependencies, is it coming from "testnet" or "mainnet"?

btspoony commented 1 month ago

from testnet

chasefleming commented 1 month ago

@btspoony did you try the dependencies install before or after the testnet migration?

chasefleming commented 1 month ago

@btspoony can you share your flow.json?

btspoony commented 1 month ago

It is completely new and started after the testnet migration.

I have added all to contracts then it works. Now any new flow.json using flow-c1 should have this issue.

https://github.com/33-Labs/flowview/pull/18/files#diff-cd9c6c92890660a891a33cf9476da63a4c512806b90a1d522dd907e576801e2c