Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

more customisable padding

Open
#174 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

Start by locating the component's existing uniform padding prop and its usage in the editor. Check how showLineNumbers and rehypePrism affect layout, then verify that directional padding supports the requested left-heavy spacing while preserving uniform padding behavior and keeping line numbers visible.

Written by the indexing model from the issue text.

Description

Hi

I love this package, its very useful. Thanks

Is there a way to use padding in a specific direction instead of the uniform padding prop whish applies the specified number on all sides.

I want to have padding on the left larger than top, bottom and right because I'm using showLineNumbers with rehypePrism which automatically sets my line numbers for each line and also accurately skips numbering a line for lines that go over multiple lines.

when I use CSS to add the line value as content before the line and shift that in front of the line, if there is no padding it will move off the area and not be visible. If I use a larger padding all these problems disappear and it visible and is much more simple to implement.

So, prop for padding be able to accept an array of numbers in the same order as CSS

e.g.
padding: "15px 15px 15px 30px", // top, right, bottom, left
and possible a single number if people want to keep it the same for all.

thanks
john

Dominant language
TypeScript
Stars
576
Forks
23
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uiwjs/react-textarea-code-editor

All issues in uiwjs/react-textarea-code-editor

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.