Adding documentation on .js fixture files#4324
Open
reinhrst wants to merge 1 commit intocypress-io:mainfrom
Open
Adding documentation on .js fixture files#4324reinhrst wants to merge 1 commit intocypress-io:mainfrom
.js fixture files#4324reinhrst wants to merge 1 commit intocypress-io:mainfrom
Conversation
(Taking a stab at) adding documentation on `.js` fixture files. Current documentation mentions that `.js` fixture files are possible, but doesn't describe how to use them, leading to issues like cypress-io/cypress#1271 . I do think the current `.js` fixture support should get a good rethink (as mentioned 4 years ago in that issue) , but in the meantime it should have some documentation on how to use it (or fully remove any mention of it from the documentation, making it "unsupported").
|
👷 Deploy request for cypress-docs pending review. 🔨 Explore the source changes: 7618a71 |
|
@reinhrst is attempting to deploy a commit to the Cypress Team on Vercel. A member of the Team first needs to authorize it. |
|
|
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| ``` | ||
| #### JavaScript file | ||
| Cypress allows a `.js` file as a fixture, in places where JSON is expected. | ||
| The contents of this file are treated as a something that evaluates to a JavaScript object (within Cypress, the content of the file is `eval()`-ed, with parentheses: |
There was a problem hiding this comment.
Minor grammar fix: remove the article "a" from "treated as a something" -> "treated as something"
Spotted by Graphite Reviewer
Is this helpful? React 👍 or 👎 to let us know.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(Taking a stab at) adding documentation on
.jsfixture files. Current documentation mentions that.jsfixture files are possible, but doesn't describe how to use them, leading to issues like cypress-io/cypress#1271 .I do think the current
.jsfixture support should get a good rethink (as mentioned 4 years ago in that issue) , but in the meantime it should have some documentation on how to use it (or fully remove any mention of it from the documentation, making it "unsupported").