generate i18n error code

[plastikfan]

• [ ] create a formalised spec to represent errors and make sure they integrate properly with errors.Is, errors.As
• [ ] ensure appropriate use of wrapping is implemented
• [ ] create error code generator

---

• As a general rule when receiving errors from called functions, make sure you add contextual information by wrapping, either by wrapf function or by using %w inside format string

The reason why I've been having so many problems with go-i18n is because of the poor design of go-i18n, which depends on the code always importing "github.com/nicksnyder/go-i18n/v2/i18n", which is really stupid. All code with extractable content MUST import directly from nicksnyder/go-i18n/v2/i18n.

To avoid namespace clashes, we'll name local localisation folders locales instead of i18n. Unfortunately we have to accept that i18n is reserved for go-i18n because of the issue recently discovered.

See:

• best practices - logrocket

[plastikfan]

created ginkgo snippet:

• $1: the core name of the error (should not include Err or Error in its name)

  "Ginko Variable Native Error": {
    "scope": "go",
    "prefix": "gverrt",
    "body": [
      "Context(\"$1 error\", func() {",
      "  When(\"given: matching error\", func() {",
      "    It(\"🧪 should: affirm\", func() {",
      "      err := core.New$1Error(\"bar\")",
      "      Expect(",
      "        core.Is$1Error(err),",
      "      ).To(BeTrue(),",
      "        \"error does not match $1\",",
      "      )",
      "    })",
      "  })",
      "",
      "  When(\"given: non matching error\", func() {",
      "    It(\"🧪 should: reject\", func() {",
      "      err := errors.New(\"fake\")",
      "      Expect(",
      "        core.Is$1Error(err),",
      "      ).To(BeFalse(),",
      "        \"not matching error should not match $1\",",
      "      )",
      "    })",
      "  })",
      "})",
      "",
    ],
  },