You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And dev could tell to zero which folders he wants to be routed using arguments:
$ zero pages api
Interesting to remember that the .zeroignore file should still work to ignore files within the whitelist, for exemplo to ignore folder "middlewares" inside "api".
The text was updated successfully, but these errors were encountered:
Missed this!
So one possible workaround is to use the existing .zeroignore file in the following way:
# Ignore everything*# But descend into directories!*/
# Recursively allow files under a folder!/pages/**!/api/**# But also ignore a sub-sub folder
/api/middlewares/**
Does this solve the issue for your use case? Having a separate whitelist feature may get confusing.
For example, consider this project structure:
And dev could tell to zero which folders he wants to be routed using arguments:
Interesting to remember that the .zeroignore file should still work to ignore files within the whitelist, for exemplo to ignore folder "middlewares" inside "api".
The text was updated successfully, but these errors were encountered: