From 74799e25096bb9ef623f2adb40ea9a69326232c1 Mon Sep 17 00:00:00 2001 From: Andy Friesen Date: Tue, 8 Apr 2025 15:11:16 -0700 Subject: [PATCH] Update abstract-module-paths-and-init-dot-luau.md --- docs/abstract-module-paths-and-init-dot-luau.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/abstract-module-paths-and-init-dot-luau.md b/docs/abstract-module-paths-and-init-dot-luau.md index 66a2613..240848c 100644 --- a/docs/abstract-module-paths-and-init-dot-luau.md +++ b/docs/abstract-module-paths-and-init-dot-luau.md @@ -110,7 +110,7 @@ name of the current source file in order to know what `require('./foo')` will do, and if a developer renames a file to or from `init.luau`, they will be forced to rewrite every `require()`. -We can mitigate this with a new lint: If a module is the parent of other +We could someday mitigate this with a new lint: If a module is the parent of other modules, it is poor style for it to directly import sibling or parent modules. Files named `init.luau` should never issue a require that resolves to a sibling module. In our example, we would warn if `package/init.luau` were to