You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The emulator connection has been a frequent pain point in the VSCode extension and it's time that we rip it out for a number of reasons:
It degrades user experience by introducing a number of configuration hurdles and bugs. The extension is no longer a plug-and-play Cadence tool, it's a fully-fledged flow client. It should be a Cadence extension for helping developers write Cadence better
The features provided were not particularly useful. Flow client capabilities belong in a tool like the CLI, and generally speaking most interactions with the chain will be either scripted (i.e. tests) or at the application level (i.e. FCL/dev wallet)
It doesn't do what it's supposed to well. Transaction/script arguments are clunky, difficult to use. Account management is confusing. It doesn't play nice when the emulator is connected to other tools, the list goes on.
It doesn't encourage a good development process. We should instead be pushing people into the Cadence Testing Framework to test their expected states, not running scripts ad-hoc and visually inspecting the result
It meant parsing flow.json in javascript. This was a recipe for disaster as far as bugs go.
The list goes on. There's really no compelling reason to have these features and they are the cause of 99% of the emulator issues seen today.
The text was updated successfully, but these errors were encountered:
The emulator connection has been a frequent pain point in the VSCode extension and it's time that we rip it out for a number of reasons:
flow.json
in javascript. This was a recipe for disaster as far as bugs go.The list goes on. There's really no compelling reason to have these features and they are the cause of 99% of the emulator issues seen today.
The text was updated successfully, but these errors were encountered: