Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Refactoring does not update reference to file after renaming package

See original GitHub issue

-README.md (containing a link to infoA.md)
-packageA
--infoA.md

Rename packageA Result: Reference in README.md is not updated

2.7.0.40

Issue Analytics

State:
Created 5 years ago
Comments:11 (9 by maintainers)

Top GitHub Comments

1reaction

vschcommented, Jan 25, 2019

@igorwojda, found a use-case for refactoring packages which does not update links to directories.

Fix: package rename to sub-package did not adjust links to subdirectories of original package. ie. rename package abc to abc.xyz would not refactor links for abc/def to abc/xyz/def.

EAP update with a fix for the issue is available.

Installing EAP Plugin Version

1reaction

vschcommented, Jan 14, 2019

@igorwojda, thank you.

Only users who bother to report issues get to find this out. There is a whole slew of “users” who think bitching and giving low star rating on the plugin page is their best plan of action, without ever reporting an issue or contacting me via e-mail to see if it a plugin issue or something else.

When an issue is reported, to me it is a signal that someone is using the feature and that its failure is serious enough for them to take the time to report it. Usually, this is all the motivation I need to fix it.

I appreciate all bug reports and suggestions. In almost every case the result is a better plugin, with functionality I find indispensable after I implement it and wishing I had implemented it earlier.