Switch to hard-coded error messages

[adrianeboyd]

No description provided.

[svlandeg]

I see why we'd want to have these locally, but how do we plan on numbering them in the future, making sure there's no duplicate usage of the same number?

[adrianeboyd]

Good point, I guess the error codes could be customized per package, but then we have to customize add_codes. Hmm...

[adrianeboyd]

Or we have hard-coded error messages without codes here that are copied at the point when this was transferred?

[adrianeboyd]

Or maybe we can just customize ENNN?

[adrianeboyd]

Not the most attractive error message I've ever seen, but eh?

[adrianeboyd]

I don't think the other packages use error codes, so maybe hard-coding is easier.

Ah, this is also in spacy-legacy. But if this becomes a more independent package, we need something else than maintaining the errors in spacy, which is going to be a headache.

[svlandeg]

Hardcoding would actually be fine by me. Like you said we need to be able to update this package independently, it's going to be a hassle otherwise.