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.
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: colorio.js patch mocking CSS #4456
fix: colorio.js patch mocking CSS #4456
Changes from 29 commits
6a1f4ec
d391a0c
2ef636d
c62613f
920c990
576dc99
5c39c29
841fb7d
69b80f5
edf803a
3a7b7e6
eff6ad3
4fada62
71cc2b4
ebd2e96
57de085
89b7386
4e6682d
0cb35e9
af79b8b
2a4d76c
20a8a6f
c5444fd
ac45ddf
208377a
acbbc38
ad0d80e
64be6d1
b79bae4
1785f2c
e1c1eae
87c7845
8b78165
ae68dc8
a2842f4
3ae8d35
9c255b1
3271c2e
434173b
283dca9
09a36d5
ca3091a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
At some point, we're going to have to stop adding tasks to Grunt if we're ever going to get rid of it.
Should now be that time?
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.
Would be happy too, if we know what we'd rather do instead. @WilcoFiers suggested this should be in the build step. Thus there are multiple ways we could do this:
package.json
package.json
with&& cp path... && npx patch-package name...
etcI'm of the opinion that build tools are changing all the time and it makes it feel strange to suggest just switching to the new hotness, but that just writing more custom node scripts in
/build/*
results in us reinventing the wheel. Still, moving towards vite/esbuild etc in the future may be my minor preference.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.
Since we want this to be part of the build it needs to go in the grunt
build
step sonpm develop
builds it as well. We won't be moving off grunt any time soon and not in this PR so a grunt step is fine for now.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.
I don't think I said it needed to be in grunt :P. We did a good while back agree not to add more grunt tasks if we could at all avoid it. It seems viable to put this work in prebuild / predevelop scripts instead. Did you try that @gaiety-deque? If that was more difficult I can live with a Grunt solution, but if we can avoid these extra dependencies + more grunt tasks I think that's the way to go on this.
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.
Apologies @WilcoFiers I didn't mean to imply that you explicitly said it had to be in the grunt build step, just that the issue requested it be a part of the build step. Since our build step just calls "grunt" currently and the pre/post build steps were more test-like in nature it felt like we were intentionally doing these things in grunt.
Made a change 1785f2c to move it to be commands run in the package json scripts.