kee-oth

Hi! Is there a timeline on this task? Thanks!

If the current maintainers are unwilling or unable to continue work on this library, maybe they would consider transferring ownership to some community members that are interested in maintaining it.

@getify Pros 1) Developers don't have to import `documentation` function 2) Better for quick documentation 3) Clearly a TypL enhancement Cons 1) I worry that would get a bit unwieldy...

Another option that would make exporting/importing documention pretty easy. We could curry the documentation function if the function isn't supplied: ```javascript // commonDictionary.docs.js export const organizationId = string`the id for...

The above idea also makes sharing definitions really easy: ```javascript // commonDictionary.docs.js export const organizationId = string`the id for an organization` export const organizations = string`a list of organizations` ```...

Ah, ok. There's a little more to this than I gleaned from the documentation. Your explanation makes sense. For primitive data types though, is it possible to use the the...

Thanks for the detailed response! I see what you mean. Thought No.2 was on my mind, I'm generally more in favor of One Way to Do It myself so I...

@getify Thanks for the response! I appreciate your stances on bringing typing to JS. Leaving JS as JS is important and will cause a lot less friction with tooling and...

@getify Thanks! With regards to documentation, could you see TypL supporting it's own documentation style? It would be amazing to include these details for runtime debugging or integrations with IDEs....

@getify I think generating external documentation should be possible but, at this moment, I'm mainly thinking of ways to support and enhance TypL with it so TypL has even more...