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
When the step implementation files are updated (e.g. via a git pull) it can sometimes take a little while for the Gauge VSCode plugin to pick up the new steps and thus can sometimes show errors in a specification (saying the step is invalid) when it isn't. This normally resolves itself eventually but I wondered if there is a way to "force" this to happen. I think normally closing/opening code works but would be nice to have something quicker. I'm not sure how the validation is happening behind the scenes but is there a way I can force it to reset / re-validate within the VSCode?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When the step implementation files are updated (e.g. via a git pull) it can sometimes take a little while for the Gauge VSCode plugin to pick up the new steps and thus can sometimes show errors in a specification (saying the step is invalid) when it isn't. This normally resolves itself eventually but I wondered if there is a way to "force" this to happen. I think normally closing/opening code works but would be nice to have something quicker. I'm not sure how the validation is happening behind the scenes but is there a way I can force it to reset / re-validate within the VSCode?
Beta Was this translation helpful? Give feedback.
All reactions