"Test" module is documented as a type

[Altai-man]

Problem or new feature

(this is more a ticket for myself, so no hurry)

We have documented type (again, type) "Test" at https://docs.raku.org/type/Test which actually talks about a module, which is really odd to have it placed there, since no such type exists in Raku language.

Suggestions

1)Once we have a website, place a nice hand-crafted redirect.
2)To move this page somewhere where it belongs, somewhere in "Language" section.

[coke]

Good Catch! https://docs.raku.org/type.html shows it's the only module listed in with the types, and https://docs.raku.org/language/nativecall shows the other module we include.

[Altai-man]

Yup. I noticed that when generating type categories for index pages and noticed some of them specified in actual pod files (notably "metamodel" and "module") are not specified in config.json, thus not present in menu etc.
Anything once we can handle sane redirecting with fast page serving...

[JJ]

There's no such thing as a module in the index; they're all "Types". Nativecall lacks a a proper "type" page, which is basically why it's not there. That was a judgement call, I guess. "Types" and "Language" follow different indexing rules, for once; "Types" are expected to have methods, subs and so on; also Language pages don't get loaded up with graphs and superclass methods. If I had to point out an error, that would be Nativecall being only in Language and not in Types. But the word "types" was chosen before Test and Nativecall were decided to be included there. A change of stub name is, for the time being, out of question (besides, what would that be? packages?). But clarifying that "types" refers to "types, modules, and also a few routines that don't go in any of them -- that would be independent-routines" is probably in order.

[JJ]

Come to think of it, modules don't really need the addition of supertypes or type graph. So maybe it should have some special treatment.