search

Nethereum / Nethereum.Playground

Compile and run Nethereum snippets on the browser
MIT License
27 stars 17 forks source link

Update 1001.txt #42

Closed moodmosaic closed 3 years ago

moodmosaic commented 3 years ago

Remove unused reference.

juanfranblanco commented 3 years ago

Thanks, but I want to keep those references, to allow users autocomplete when experimenting.

moodmosaic commented 3 years ago

Oh, I see. Perhaps we can at least sort/order them? e.g.

  using System;
  using System.Text;
- using Nethereum.Hex.HexConvertors.Extensions;
  using System.Threading.Tasks;
+ using Nethereum.Hex.HexConvertors.Extensions;
  using Nethereum.Web3;
juanfranblanco commented 3 years ago

Yes, good idea, all examples will need to be migrated to Nethereum 4.x so it will be a good time to sort that out for all examples. BTW I love hedgehog, when I add the capability to add Validators to all the contract interactions it will be great to add examples to add tests with Hedgehog.

moodmosaic commented 3 years ago

I'd be happy to help ❤️ We also support LINQ via Hedgehog.Linq namespace (example).

juanfranblanco commented 3 years ago

Yes I saw that, it is great. I will surely will need your help to create a good example. My thought for years was to put a generic validator "interceptor" based on Types, and specific contract, (when sending / signing / estimating a transaction, making a query, etc) so simply ending up with a registry of validators. This is another reason for separating Commands and Queries per FunctionMessages, DeploymentMessages, etc. So here it can fit very well, there were also other people on the community thinking of using f# to create some generic kind of Plex tester, so my guess is that they thought of hedgehog too.