Skip to content
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

doMakeSameDomainsLinksRelative somewhat counter-intuitive #79

Open
S1SYPHOS opened this issue Jun 25, 2022 · 0 comments
Open

doMakeSameDomainsLinksRelative somewhat counter-intuitive #79

S1SYPHOS opened this issue Jun 25, 2022 · 0 comments

Comments

@S1SYPHOS
Copy link
Contributor

What is this feature about (expected vs actual behaviour)?

While all options receive bool (which is intuitive, because their name suggests that you DO it or you DO NOT do it), doMakeSameDomainsLinksRelative receives an array while also being named do(...). This might lead to some confusion (plus TypeError).

I guess changing its name to something like makeSameDomainsLinksRelative could work, but ultimately, the desired array would be better off as global object $this->sameDomains (array) being set by setSameDomains (or whatever) containing the logic doMakeSameDomainsLinksRelative contains right now - so when 'activating' the option via doMakeSameDomainsLinksRelative, this would receive a bool.

How can I reproduce it?

Thinking about the naming convention - and eventually passing bool to function doMakeSameDomainsLinksRelative.

Does it take minutes, hours or days to fix?

Me: Hours
You: Seconds 😄

Any additional information?

It's rather the observation of a (tiny) inconsistency rather than a real problem, I totally get that, anyway I thought it's something to think about and make an informed decision 🦊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant