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

Go to test #162

Open
AdrienLemaire opened this issue Oct 9, 2022 · 1 comment
Open

Go to test #162

AdrienLemaire opened this issue Oct 9, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@AdrienLemaire
Copy link

AdrienLemaire commented Oct 9, 2022

Describe the feature
On VScode, an option "go to tests" exists, that will:

  • navigate the user to the related test file if exists,
  • else create the directory structure and filename, and fill the new file with boilerplate to get started writing the test.

It would be nice to have the option to :CocCommand flutter.goToTests and get the same behavior on vim :)

@Kavantix Kavantix added the enhancement New feature or request label Mar 22, 2023
@dkbast
Copy link

dkbast commented Mar 27, 2023

yes this would be amazing - a next logical step would be that renaming/moving one file also results in renaming/moving the other file. This could maybe also be done via a custom_lint rule e.g. "have matching paths and names for test and implementation"'

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

No branches or pull requests

3 participants