adapt library for cadence1

[NtTestAlert]

Closes #224

Description

Various changes to support Cadence 1.0 emulator
All tests are passing

I've changed the workflow to use Cadence 1.0 CLI
This will need to be reverted later on

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[changeset-bot]

⚠️ No Changeset found

Latest commit: ac55d57

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[jribbink]

Hey @NtTestAlert , thanks for the PR! I will review this & try to release it today :)

[NtTestAlert]

Hey @NtTestAlert , thanks for the PR! I will review this & try to release it today :)

Hi, there is one more thing to be done, stable-cadence cli adds -c1 suffix (but only in some versions), and a version check in general would be good.
Will add it in soon.

[NtTestAlert]

Added execName param to emulator, defaulting to flow-c1

With additional changes (support for old transactions/scripts) might allow users to mix emulator versions, in order to test migration. But that is out of the scope of this PR

[jribbink]

I tried getting CI to work, but I'm having issues so I guess I can just run locally to verify for now (I force pushed to roll back some of my failed attempts to fix it)

I just ran the tests and it looks good, but it seems like signer parsing fails for an entitled account reference as a signer (e.g. auth(SaveValue) &Account as oppose to an unauthorized reference &Account), which is generally speaking what users will be using in their transactions.

Are we able to support this? Seems like it might be a blocker for any real usage of the library?

[NtTestAlert]

The tests for flow-js-testing pass, incl those with authorized signers - it doesn't try to parse them before executing AFAIK
However flow-cadut does not properly parse authorized signers as per other PR, added a fix there.

Pipeline failed because it could not parse version due to the upgrade banner, bypassed by adding --output json to "fool" flow-cli

[NtTestAlert]

Still need to adapt the library to work with shorthand imports
(import "ViewResolver")
In my project I have this hooked in jest and with some regexes that expand it to import ViewResolver from "./ViewResolver.cdc"
I'll try to add it to the library today
Added workaround until flow-cadut is updated

[jribbink]

Awesome!! I've brought this up to date with the latest @onflow/flow-cadut@stable-cadence release & will merge this, release -> @onflow/flow-js-testing@stable-cadence. Thank you for your contribution!