-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix: component spec creation with spec pattern #19862
fix: component spec creation with spec pattern #19862
Conversation
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
…jandro/fix/component-spec-creation
…jandro/fix/component-spec-creation
…jandro/fix/component-spec-creation
…press-io/cypress into alejandro/fix/component-spec-creation
@@ -47,7 +47,7 @@ const isRunMode = window.__CYPRESS_MODE__ === 'run' | |||
// requests, which is what we want. | |||
const query = useQuery({ | |||
query: SpecPageContainerDocument, | |||
requestPolicy: 'cache-and-network', | |||
requestPolicy: 'cache-only', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
import { unionType } from 'nexus' | ||
|
||
export const GeneratedSpecResult = unionType({ | ||
name: 'GeneratedSpecResult', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did not know about this, very nice
baseName: 'Basic', | ||
fileExtension: 'tsx', | ||
contents: `it('should do stuff', () => {})`, | ||
currentProject: ctx.currentProject, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting to wonder how useful the stubgql mutations are, they are really hard to keep up to date w/ real data
@@ -358,6 +395,28 @@ export class ProjectActions { | |||
|
|||
const [newSpec] = codeGenResults.files | |||
|
|||
const cfg = this.ctx.project.getConfig() | |||
|
|||
if (cfg) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure when or where but we really need to centralize this - it's a copy paste of some really complex and important code
* 10.0-release: (25 commits) fix(unify): improve dev server config ergonomics (#19957) feat: add spec pattern modal (#19801) fix: Windows e2e project scaffolding issues (#19938) feat: update @cypress/schematic to use proper e2e config for 10.0.0 (#19827) fix: correctly migrate projects with custom integration folder (#19929) fix: component spec creation with spec pattern (#19862) fix: missed committing yarn.lock after merge conflict fix: correct reference branch / commitSha in performance-reporter (#19941) feat: update navbar UI per Figma (#19926) fix: seed examples files when no e2e directory is created (#19768) chore: remove windy lightBlue warning test: component test updates (#19925) feat: Focus browser from select browser screen and on dashboard login (#19842) test: Honeycomb system-test reporter (#19855) fix(deps): update dependency engine.io to v5.2.1 [security] feat: Retain fileName when working with aliased fixtures and files (#19820) Update release-process.md Update release-process.md Update release-process.md Update release-process.md ...
User facing changelog
Additional details
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?