Skip to content

Conversation

PratikforCoding
Copy link

Related Tickets & Documents

Fixes: #[2515]

Description

  • In the Keploy repository there is issue #2515 which states that there is weird colon after the Author by and Reviewed by section. I fixed that. along with that I saw the copy button is also replicated to the Table of Content, which has no use and make the look weird, so I removed that also from the Table of Contents section but it is still there in the blog body.
  • Along with that I saw the copy button is also replicated to the Table of Content, which has no use and make the look weird, so I removed that also from the Table of Contents section but it is still there in the blog body.

Changes

  • Takes the original headings array prop
  • Creates a new array where each heading's title is cleaned
  • Uses regex /#\s*$/ to remove hash symbols at the end
  • matches the hash character

  • \s* matches any whitespace after the hash
  • $ ensures we only match at the end of the string
  • .trim() removes any remaining whitespace

Type of Change

  • Chore (maintenance, refactoring, tooling updates)
  • Bug fix (non-breaking change that fixes an issue)
  • New feature (change that adds functionality)
  • Breaking Change (may require updates in existing code)
  • UI improvement (visual or design changes)
  • Performance improvement (optimization or efficiency enhancements)
  • Documentation update (changes to README, guides, etc.)
  • CI (updates to continuous integration workflows)
  • Revert (undo a previous commit or merge)

Testing

  • Just used npm run dev and saw it working

Demo

  • Before
Screenshot 2025-06-18 at 3 43 21 AM
  • After
Screenshot 2025-06-18 at 5 32 40 AM

Environment and Dependencies

  • New Dependencies:
  • Configuration Changes:

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added corresponding tests
  • I have run the build command to ensure there are no build errors
  • My changes have been tested across relevant browsers/devices
  • For UI changes, I've included visual evidence of my changes

Signed-off-by: PratikforCoding <kotalpratik@gmail.com>
@amaan-bhati
Copy link
Member

Hey @PratikforCoding Thanks for creating this pull request. Can you please ensure that you have ran npm run build before raising the pr, please add a screenshot too.

@PratikforCoding
Copy link
Author

Hey @amaan-bhati I had not run npm run build before pr but after watching you comment I synced my fork with the main branch of blog-website repo and then ran npm run build and here is the result, I am providing the screenshots:
Screenshot 2025-06-20 at 3 52 53 PM
Screenshot 2025-06-20 at 3 53 00 PM

please update me with farther instructions, thanks for looking into this pr!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants