-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correctly parse and implement netlify.toml #1
Comments
netlify.toml
Ps. I don't use |
… a file, added redirect status support #1
…ch will be used for cli context override #1
Turns out Netlify redirects aren't actual redirects 🤦♀️ Not sure how I missed it, just finished reading Netlify's Redirect Docs and it's not looking good for redirects support... this is going to be a major feature to implement, I'll try and break it down as logically as possible and provide a checklist in another issue. 🙈 |
Closing in favour of #8 |
Netlify doesn't clearly specify required properties for
toml
configs and testing what happens within different scenarios is a pain so for the purpose of simplifying things I think it's best to enforce explicit withtoml
configurations, for example an error will be thrown if the static router is being initialised but there is nobuild.publish
property specified.Context
-c --context
option to override.base
prop.Redirects
from
,to
prop.status
prop.force
prop (could be tricky).query
prop (could be tricky).conditions
prop (could be really tricky).headers
prop.Headers
for
prop.The text was updated successfully, but these errors were encountered: