-
Notifications
You must be signed in to change notification settings - Fork 260
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
Inline SCSS (close #158) #160
Conversation
b2640aa reverts the version bump back to |
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.
@Bernd-L thank you for taking the time to put this PR together! I hope my review response is not too overwhelming. It is not easy to communicate this via text, but all of my review here is in good heart!
Overall, I would say 95% of this PR is not actually related to the one thing this PR "should" be about. For that last 5%, it is well-crafted.
For future PRs, my primary advice would be to start small. Do the absolute minimum to solve your problem. If you really want to write more code and refactor more stuff (which I totally understand), please do so in a separate PR ... and typically it would be a good idea to ask the maintainers if such is even welcome. Style is subjective. Naming is subjective. I'm sure you take my point.
The reasoning behind my recommendation here is that the cognitive load gets higher and higher as changes are added. This can lead to bugs and other such undesired behavior as review becomes more difficult. Ping me for another round of review when you are ready.
Cheers! Let me know if you have any questions! Happy hacking.
@Bernd-L also, very importantly, I would highly recommend that you squash all of your commits down to a single well-formed commit. A single title line describing the high-level of what you've done, followed by a more descriptive paragraph describing what you've done. Better that you have control over that than me having to squash it all down before I merge. |
My latest commit f72448a aims to revert all undesired markdown changes but keep all spelling fixes and doc updates. Let me know if you want further changes to the format reversal. |
Allows for compiling and then in-lining SASS and SCSS using a new data-inline attribute in a data-trunk link tag. Compiling SASS and SCSS without inlining is still supported. This commit also fixes several spelling mistakes and updates documentation to reflect the changes. A non-squash version can be found at Bernd-L:inline-scss_no-squash, in case you want to see individual commits or for reverting individual changes.
@thedodd I have now squashed all my commits into one single commit. Please note that a commit from @lukechu10 is also present, since it was made ~9 hours ago, and I couldn't squash it into this pull request. I hope this PR is now good enough for a simple merge (without further squashing on your end). My commit message reads as follows:
If you need any further changes, let me know. |
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.
Awesome! Thanks for all of the work here @Bernd-L, and thank you for responding kindly to my review comments!
I've left a few comments here, but I am just going to address them once I merge. Cheers!
@thedodd Dies this mean that my commit will be part of the main branch? That'd be nice, I'm looking forward to the next release too. |
@Bernd-L done. |
Thanks! It's great to see my first contribution (to an actual codebase, not just Docs) get merged 😊🎉🚀 |
@Bernd-L grats! Thanks again for all of the hard work here. |
This PR is supposed to close #158.
Checklist