Open evenstensberg opened 5 days ago
Your PR was set to target main
, PRs should be target develop
The base branch of this PR has been automatically changed to develop
, please check that there are no merge conflicts
Hi @evenstensberg thank you for your contribution. Our cypress tests seem to be struggling to find webpack with this new folder structure, please could you take another look to see if there's a way they can work with this? Thanks again 😊
@GCHQ-Developer-530 The test suite is running, but there's runtime errors. I think there's something wrong with the configuration still, fixing it later.
@GCHQ-Developer-530 I think it should work now. Could you run locally and verify?
Also, I'm very interested in contributing more to your repositories, and maybe I'm lucky to get some swag :D
If you need help with infrastructure, react or anything related to build tools, I'm happy to help. I've done some work for other organizations that might suit your needs well, such as adding cspell
, which is a grammar linter for code.
Let me know what you think :)
@evenstensberg Looks like that's worked, thank you so much! We'd love for you to contribute anything you feel could improve our repo, please feel free to open pull requests and the team will have a look 😊 In relation to swag, I spoke to the team and we should be able to think about it after some more contributions!
Just one comment from me before it should be ready for approval, please could you amend your commits so that there is only one commit per scope e.g. one commit for the react changes, one commit for the fonts changes, and one commit for the canary react changes?
@GCHQ-Developer-530 Great! Before eventually merging, test everything locally first. It is important that the behaviour is correct and sometimes things break with 3rd party webpack usage (most tools are flexible around webpack, but cypress is very verbose).
RE: swag -> My email is evenstensberg@gmail.com, if you need my physical address, send me an email.
The commits are now scoped. In the future when using webpack, the normal convention is putting it in a .webpack
folder, and defining context (where webpack should run, its like process.cwd) is used to have identical behaviour as a root webpack.config.js
.
Let me know if you have any questions.
Summary of the changes
Just improving a bit of repo infra
Related issue
N/A
Checklist
General
Testing
Accessibility
Resize/zoom behaviour
System modes
Testing content extremes