I just discovered that Android-Studio-Refactoring-Scope issue, has appeared in the latest SNAPSHOT build which ignores the selected refactoring and find usages scope and always use “Modules with dependents, scratches and consoles” even if “All Places” or “Project Files” is selected for java class files in the project view.
This causes a problem for Markdown Navigator refactoring because often the markdown files are in the project scope but not in any module. Resulting in links to Java and Kotlin files not being refactored or shown in find usages.
If the markdown file is placed under a module then everything works as expected.
Files such as version history or README are usually at the project root and not in any module and moving them to a module is not possible.
This used to work correctly in all JetBrains IDEs which I tested previously and today I noticed that it no longer works.
The optimization of using consoles & scratches, union module with dependents on class files only makes sense when searching for code references. Other types of references could be located in Project files which the passed scope ignores.
If I ignore the passed in scope and use project all scope then find references does return link references from Markdown. However, Go To Declaration or Usages ignores these references. The same for rename refactoring which leaves these links unchanged causing broken links.