fix(desktop-gui): correctly display component and e2e config values

[lmiller1990]

• Closes In Desktop GUI, e2e and component in config display as [object Object] #16269

User facing changelog

Fix a bug where e2e and component configuration values were not correctly showing in the Cypress launcher.

Additional details

It looks like in the original PR that implemented this feature, we intentionally removed the component and e2e values when merging the config. This makes the actual cypress.json config and what's shown in the Desktop GUI different, which could be lead to confusion. This PR changes the behavior and leaves the overridden values in the config object, even after merging them based on testingType.

How has the user experience changed?

• show {} for empty object
• correctly show e2e overrides:

PR Tasks

• Have tests been added/updated?
• Has the original issue or this PR been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?
• Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

9518 • 0 • 111 • 3 • 0

---

Run details

Project	cypress
Status	Passed
Commit	f7ae7be
Started	Apr 30, 2021 3:03 AM
Ended	Apr 30, 2021 3:15 AM
Duration	11:21 💡
OS	Linux Debian - 10.8
Browser	Multiple

View run in Cypress Dashboard ➡️

---

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

[jennifer-shehane]

I kind of get the initial motivation, but this makes more sense to me to show both objects. I can see the config passed, but also still evaluate what the resolved config is in the main object.

This also used to be weird if you tried to console.log the config object from your plugins file. If you passed a bunch of config to e2e, it would just be empty. That's been fixed also in this PR.

This looks good and is tested. Shouldn't get weird [object Object] in the future also.

[cypress-bot]

Released in 7.3.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v7.3.0, please open a new issue.