4 ms·
Is there any way to "ignore" specific files or directories? For example, I want to reuse React components across different routes (exposed as jsx files). Howeve
by sjroot 8y ago
Is there any way to "ignore" specific files or directories? For example, I want to reuse React components across different routes (exposed as jsx files). However, I don't want `mysite.com/components/Container` to be a valid endpoint.
- deleted 8y ago[deleted]
- sjroot 8y agoI would propose adding support for a 'zeroignore' file to handle this. :)
- asadlionpk 8y agoYes. It's not written in docs yet but any file or folder starting with _ (underscore) is not exposed publicly. This feature spec is still open for discussion as on how to tackle it the best.
- sjroot 8y agoCheck my reply to this comment. The underscore idea was one of the first things to come to mind too, but I think having a specific file makes it clear to others who might not understand Zero internals.
- asadlionpk 8y agoYou are right. A .zeroignore file seems like a good idea.
- jermaustin1 8y agoWould that not count as a configuration file though?
- shadofx 8y agoYou can still configure zero conf frameworks, it's just not explicitly required for it to function
- gumbo 8y agoHere we go. Zero conf :-)
- jypepin 8y agoseems like doing something like Next.js might be a better choice, aka have a main folder that exposes publicly accessible files, instead of having to add _ to each folders that should be private (it seems to me most folder/files would be private and not the other way around)