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
In this ticket, you should implement the "detection" part:
check node_modules (we've got some patterns for this already)
look for modules matching some pattern (right now it's cypress-ct-*
Validate it looks good and aligns with the format outlined in the tech brief
Add some code to perform this check, probably when Cypress starts up if they have no configured component testing yet
functiongetThirdPartyWizards(){// check node_modules// find 0 or more modules// validate them// return array_of_valid_modules (invalid are just silently ignored, up the the author to test their module works)}
Assume you will have a function exported from cypress called defineComponentFramework. That is implemented in this PR.
These will be merged with our first party frameworks and all shown in the onboarding wizard.
If there's any ambiguity, reach out and ask 💯
The text was updated successfully, but these errors were encountered:
Based on the work done in the technical brief: #24991.
Given a third party module that matches the format in the tech brief,
cypress-ct-*
, we show this in Launchpad.Note, there are some minor changes to the brief: https://github.com/cypress-io/engineering-documentation/pull/67
In this ticket, you should implement the "detection" part:
node_modules
(we've got some patterns for this already)cypress-ct-*
Assume you will have a function exported from
cypress
calleddefineComponentFramework
. That is implemented in this PR.These will be merged with our first party frameworks and all shown in the onboarding wizard.
If there's any ambiguity, reach out and ask 💯
The text was updated successfully, but these errors were encountered: