Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
One of the benefits of having the compiled CSS in the revision history is that it enables you to see changes if you have other steps in the compile process besides SCSS -> CSS. One example is if...
Answer
#2: Post edited
by
mbomb007
·
2020-10-22T19:01:44Z (over 3 years ago)
- One of the benefits of having the compiled CSS in the revision history is that it enables you to see changes if you have other steps in the compile process besides SCSS -> CSS. One example is if you use [auto-prefixer](https://github.com/postcss/autoprefixer), which automatically adds vendor prefixes to CSS in order to support your target browser versions and ensure adequate market share coverage (see [Can I Use](https://www.caniuse.com/)). There are all sorts of [PostCSS](https://www.postcss.parts/) plugins available.
- With the example of an auto-prefixer, the SCSS code doesn't have to change for the output to change. If a browser updates, the CSS might update. If the users switch from one version to another, that could change the browsers or versions you might prefer to support. If your SCSS doesn't change, but the CSS does, it's preferable to have the CSS in the revision history.
Another benefit of revisioned CSS is that you can include compiler comments in the CSS output that show what line and file in SCSS each CSS line came from. This speeds up the debugging process if you have an issue occur or make a mistake.
- One of the benefits of having the compiled CSS in the revision history is that it enables you to see changes if you have other steps in the compile process besides SCSS -> CSS. One example is if you use [auto-prefixer](https://github.com/postcss/autoprefixer), which automatically adds vendor prefixes to CSS in order to support your target browser versions and ensure adequate market share coverage (see [Can I Use](https://www.caniuse.com/)). There are all sorts of [PostCSS](https://www.postcss.parts/) plugins available.
- With the example of an auto-prefixer, the SCSS code doesn't have to change for the output to change. If a browser updates, the CSS might update. If the users switch from one version to another, that could change the browsers or versions you might prefer to support. If your SCSS doesn't change, but the CSS does, it's preferable to have the CSS in the revision history.
- Another benefit of revisioned CSS is that you can include compiler comments in the CSS output that show what line and file in SCSS each CSS line came from. This speeds up the debugging process if you have an issue occur or make a mistake. And if you ever need to revert your code changes, you don't have to wonder what the resulting CSS you get on your production environment will be.
#1: Initial revision
by
mbomb007
·
2020-10-22T19:00:41Z (over 3 years ago)
One of the benefits of having the compiled CSS in the revision history is that it enables you to see changes if you have other steps in the compile process besides SCSS -> CSS. One example is if you use [auto-prefixer](https://github.com/postcss/autoprefixer), which automatically adds vendor prefixes to CSS in order to support your target browser versions and ensure adequate market share coverage (see [Can I Use](https://www.caniuse.com/)). There are all sorts of [PostCSS](https://www.postcss.parts/) plugins available. With the example of an auto-prefixer, the SCSS code doesn't have to change for the output to change. If a browser updates, the CSS might update. If the users switch from one version to another, that could change the browsers or versions you might prefer to support. If your SCSS doesn't change, but the CSS does, it's preferable to have the CSS in the revision history. Another benefit of revisioned CSS is that you can include compiler comments in the CSS output that show what line and file in SCSS each CSS line came from. This speeds up the debugging process if you have an issue occur or make a mistake.