palantir/blueprint

Running, muted, large, small, disabled props on Text component

Open

#4,163 opened on May 31, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P3Package: coreType: feature requesthelp wanted

Description

Environment

  • Package version(s): 3.28.1
  • Browser and OS versions: Firefox@dev, Mac@Catalina

Feature request

Any plans to add muted, running, muted, large, small, and disabled props to the Text component?

Examples

<Text muted>This is muted text</Text>

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
clear
Prerequisites
ReactTypeScriptfamiliarity with Blueprint component patterns
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Locate the Text component source file (likely in src/components/text/text.tsx) and review how other components like Button or Card implement similar boolean props (muted, disabled, etc.). Check if there is a pattern for applying CSS classes based on props. Also examine any existing style definitions for muted, large, etc. in the Blueprint stylesheets. Discuss with maintainers if the props should be added as part of the component's API.
Running, muted, large, small, disabled props on Text component · palantir/blueprint#4163 | Good First Issue