Hyeseong Kim

Filenames (and dirs) to allow for file system routes: - hyphenated: `with-hyphen.res` - Remix style: `$invoiceId.res` - Next.js style: `[slug].res`, `[...all].res` - Gatsby.js style: `{Product.fields__sku}.res`, `{Post.parent__(MarkdownRemark)__parent__(File)__name}.res` - vite-plugin-ssr style: `@id.res`...

It's about `.res` files. It's for filesystem routes that JS frameworks support. The way to use ReScript with it today is to create a JavaScript file that re-exports modules, which...

> Would it help to be able to control the name of .js file generated from a given .res file? Maybe, but I personally prefer using separate JS files then

1 is strange to me. In particular, it complicates the module resolution of the output. I guess 2 would be fine because they will be leaf on the module graph,...

> For this to fully work with JS conventions there also needs to be a way to have the exact same file names in multiple folders, right? correct, so I...

See https://forum.rescript-lang.org/t/standardised-exotic-modules-rfc/2852 proposed by @tom-sherman

@tom-sherman Your original proposal seems to attempt to circumvent two limits at once 1. Limit valid characters 2. Limit duplicate file names This issue is only about 1, and it...

Introducing the prefix convention potentially makes another interop limit. it is simply possible if there were another framework out there that uses the `~page.js` rule. 2 is a relatively easy...

> To sum up, what I'm advocating for is not a specific solution such as the one proposed in this issue but a general solution that can account for a...

I agreed that the existing proposal may be argonomic enough. Its complexity should not be much different from a codegen solution on the user side. One thing that is clear...