linkedin / linkedin/css-blocks

Private/Protected Objects?

Open
#8 0 comments 0 reactions 0 assignees View on GitHub
@css-blocks/core enhancement under consideration
Dominant language
TypeScript
Stars
6.3k
Forks
154
PR merge metrics
No merged PRs in 30d

Description

We should consider whether inheritance needs the notion of a private object. Marking an object as private would make it illegal to resolve with an override.

Protected would be the same but would allow overrides in sub-blocks.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Begin by tracing inheritance, override resolution, and sub-block handling in the repository, then clarify the intended private and protected semantics. Done means the design is settled and the resulting behavior is covered for both prohibited and permitted overrides.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.