netlify adapter docs: add warning on redirects file placement

[swyxio]

Before submitting the PR, please make sure you do the following

addresses #1586 to hopefully save others from the same confusion

[benmccann]

This feels quite wrong to me. _redirects isn't a static asset. There are three different directories that get copied into the publish directory. We'd just be relying on the fact that static assets end up in the publish directory, but it's quite an unintuitive place to have to put the file.

I'd rather put it at the root of the project. In neither case would we be putting it directly in the publish directory, but rather relying on the adapter to copy it to the right place. It's just a question of where would you most expect it to live. Living next to netlify.toml makes more sense than living next to your image files, etc. in my opinion

[swyxio]

i see. so perhaps @roschaefer should reopen #1586 ?

[kvn-shn]

At least to me it feels quite intuitive putting it into static/ (e.g. next to robots.txt) because it's more like an oldschool .htaccess file that belongs in the "public_html" of the server... After all it is, in the context of Svelte, a static asset that Svelte can't and won't do anything with.

So in my opinion this PR would do the trick.

[benmccann]

I went ahead and merged #1586. It shouldn't stop you from putting it in static/ if you'd like, but I think supporting it in the root directory next to netlify.toml makes a lot of sense

[swyxio]

just fyi - i think this is inaccurate - the doc actually says "Rules in the _redirects file are always processed first, followed by rules in the Netlify configuration file."

in other words you CAN put stuff in netlify.toml, AND in _redirects, its just that the latter overrides the former in cases of conflict.

[benmccann]

I believe it's true when you consider the catch-all route that gets added