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
Add URL checks to Doctor #5760
Merged
Merged
Add URL checks to Doctor #5760
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DirtyF So, replace these two lines with:
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of moving
url_exists?
out ofproper_site_url?
in a separate single test to address Parker's concern, so we test first ifsite.url
exists before launchingproper_site_url
. But as I suck at logic and programming, this is maybe a terrible idea :)If what you are proposing does that, it's fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't follow.
We really want
site.url
to be set, either manually by the user or automatically by something likepages-gem
. Ifsite.url
is blank, it is likely to cause problems and we should warn the user about this.If a user has some special reason to use a blank
site.url
then they will understand that this warning does not apply to them.On the other hand, if a user has simply neglected to set
site.url
and now things aren't working as expected, this check should alert them to the issue and suggest settingsite.url
. That is the entire point of this PR.I'm probably not understanding your concerns; can you try to explain to me again now that I've explained my intent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get you perfectly and as it's impossible to tell if a blank
site.url
is intentional or not, you prefer to warn in both cases.Maybe just make the messages more clear then?