palantir/blueprint

Exposing SASS variables as custom properties

Open

#5,181 opened on Mar 18, 2022

View on GitHub
 (3 comments) (1 reaction) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
Domain: APIP2Package: coreType: feature requesthelp wanted

Description

Environment

Any

Feature request

Have you considered exposing SASS variables as custom properties so users can write custom CSS in their applications using the values blueprint uses internally?

This could be optional and probably prefixed.

Examples

For instance, variables like $pt-grid-size could be exposed like this:

:root {
  --pt-grid-size: #{$pt-grid-size};
}

Contributor guide

Tech stack
typescriptreacthtmlcss
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
SASS/SCSS knowledgeCSS custom propertiesBlueprint build system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
The issue requests exposing SASS variables as CSS custom properties for easier customization. Investigate the repo's SASS variables (likely in packages/core/src/common/variables.scss) and the build pipeline (gulpfile or webpack config) used to process styles. A solution could add a script that generates a :root block with variables. Check existing PRs or discussions for prior attempts.
Exposing SASS variables as custom properties · palantir/blueprint#5181 | Good First Issue