add example nep11

[vikkkko]

[Jim8y]

@vikkkko nice work, may you please use dotnet format to update the format?

[cschuchardt88]

Change project name to non-divisible NEP11.

[vikkkko]

Make changes and You need to write tests in order to approve this.

Some tests will be added later.

[Jim8y]

@AnnaShaleva please check it again, the name has being updated.

[Jim8y]

please relove conflict @vikkkko

[superboyiii]

All done. Ready for merge.

[superboyiii]

@shargon All done

[Jim8y]

this is an example and unnecessarily blocked the proposal. exception or assert all make sense, not worth a debating here. Thus, i will merge.

[roman-khimov]

this is an example

Yeah, this is an example and examples get copy-pasted into production code. Which means https://github.com/neo-project/neo-devpack-dotnet/pull/1009/files#r1562443533 will soon be in many C# NEP-11 implementations. And people will refer to this as the way to do things even though we know it's not the best one.

[shargon]

this is an example

Yeah, this is an example and examples get copy-pasted into production code. Which means https://github.com/neo-project/neo-devpack-dotnet/pull/1009/files#r1562443533 will soon be in many C# NEP-11 implementations. And people will refer to this as the way to do things even though we know it's not the best one.

I can't agree more, an example in the official repository is not an example, it is a template

[Jim8y]

Yeah, this is an example and examples get copy-pasted into production code. Which means https://github.com/neo-project/neo-devpack-dotnet/pull/1009/files#r1562443533 will soon be in many C# NEP-11 implementations. And people will refer to this as the way to do things even though we know it's not the best one.

I wont block your best one example practice if you have one in your mind. But blocking a pr without telling what is your best practice is not ok for me. And i sort of not believing there exists a best one example, discussion here more like either or.