You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for opening this is an Issue. Doing so as a consequence of #45.
I'm wondering whether with the autocompletion features that exist for fixture and alias and the knowledge of the commands folder, if there's a way to have autocompletion for custom commands that I'm somehow missing.
The setup seems ok (ie. Go to Custom Command Definition works fine, as well as the fixture/alias autocompletion), so not sure if I'm missing something here or wishing for something that doesn't exist.
The text was updated successfully, but these errors were encountered:
@talyh ,
custom command autocompletion is currently supported via Cypress proposed approach with types for custom commands.
It is done by generating type definitions file on demand Generate type definitions for cypress commands and also there is automatic option to do that when file is saved (cypressHelper.typeDefinitionOnSave).
I think that it will be great to have autocomplete when there is no such definitions available. However it may conflict with definitions provided by cypress and by typescript engine, so it should be investigated first.
Sorry for opening this is an Issue. Doing so as a consequence of #45.
I'm wondering whether with the autocompletion features that exist for
fixture
andalias
and the knowledge of the commands folder, if there's a way to have autocompletion for custom commands that I'm somehow missing.The setup seems ok (ie.
Go to Custom Command Definition
works fine, as well as thefixture
/alias
autocompletion), so not sure if I'm missing something here or wishing for something that doesn't exist.The text was updated successfully, but these errors were encountered: