renyard
commented
9 years ago Hi David
Thanks for the suggestion, help for new users is something that I have been thinking about recently, with a few ideas on #36.
However, there's a few reasons why I don't want to switch on auto validate as a default:
- This will generate extra requests to the user's dev server for each page load, which may not be expected and could cause confusion. (This is in addition to the request to the validator.)
- I also want to make sure that there is capacity on the remote validator instance for intentional validation requests. Defaulting to auto validate even a subset of hosts is likely to massively increase the load on the server with an impact on performance (or an increase in cost for me :)).
- I don't have any data on usage of auto validate vs manual triggering, so I don't know if this is a feature that the majority want or use.
- localhost and 127.0.0.1 will cover most cases, but it may be confusing that other dev host names are not automatically validated.
Rather than a default, adding a quick setting to the new install page may be a better way to go. Maybe a button to set it to the common use cases and a text box to add any extras?
Thanks Ian
davidrenne
Can you add localhost, 127.0.0.1 and any other things that make sense to new installs to automatically check those?
New users might look at the green icon and think you are okay on your localhost without checking settings.
This is a dev tool, so it should work out of the box checking all your localhost urls for validity.