Serena Postelnek

From what I understand, `workspace.libraries` points to where the definitions of the library, not the library itself. I could be wrong, of course, but if I wanted to point it...

I would think that just having the documentation set up would be fine, no? Because realistically if you require the library and export globally or in pieces, it should have...

Hm.. interesting. Maybe that's a feature that would be needed to be added?

> I was able to get it to work by not using `:export()`: > > ```lua > local assert = require("libraries.batteries.assert") > ``` > > I don't know how to...

Yeah I tried not using `:export()` and still only get the basic documentation. I've been looking at all the other examples as well, but there's really nothing different on how...

fwiw - I have the definitions files hosted [on this repo now](https://github.com/TurtleP/batteries-definitions). They still don't work, but I'm not quite sure as to what may be wrong still after having...

Alright, I've solved the mystery, although there *seems* to be a bug in the language server. To fix it, I renamed all the functions in the library definitions as `batteries.{module}.{function_name}`....

> I can't find any file with path libraries/batteries. However batteries is a global variable, so you can use it without require. This shouldn't be the case. The library has...

Ah, sorry. When I mean "test environment" I am talking about as if I'm writing actual Lua code in a project, not the definitions. The screenshot I provided has the...

I think it would make more sense to align them like how various other languages are, that is, to treat each one as const separately (meaning you have to mark...