Update selectors.md - #2088
Conversation
Added a component example, with a template, to make it clear how the selectors can work
✅ Deploy Preview for vue-test-utils-v1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I have added two different ways to define the component, and I wasn't sure which one would be preferred. The main point I was trying to clarify was how the ref and name selectors can be used to select elements, with an example. Totally understand if this is too different to other testing documentation and not needed. While I'm getting more into the vue testing space, I found a bit of confusion here and thought an example would help 👍 |
|
The failed CI test looks to be related to code styling, for 7 pages, One of them I have modified. Pulling the docker image and running the prettier to determine what's wrong with the styling to fix it |
|
Unfortunately I can't find the project files in the docker image, I suspect they're added as part of the implementation details in CircleCI's 'attaching workspace' step. I haven't setup this project locally, just changed the file in github's editor. If it's needed I can set it up locally, but I don't want to spend more time on this, unless someone from So I guess, bump |
Added a component example, with a template, to make it clear how the selectors can work
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch.fix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: