SSWConsulting / SSWConsulting/SSW.Rules

🦙 Bug - TinaCMS Dependency - Unable to End Quote in Rules V3 (TinaCMS)

Open
#2,110 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

TinaCMS YakShaver
Dominant language
TypeScript
Stars
26
Forks
17
Avg merge
14h 39m
Merged PRs (30d)
2

Description

Requested by: @Marxoz via YakShaver.ai 🦬
cc: @Marxoz, @jakebayliss, @Aibono1225, @amankumarrr, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 28 sec)

  Url from screen share: https://lmstudio.ai/download

Pain

Users are unable to end a quote when editing a rule in Rules V3 using TinaCMS. Attempting to end a quote either continues the quote or removes it entirely.

Acceptance Criteria
  1. Users can end a quote without removing it entirely.
  2. Pressing 'Enter' after a quote should start a new paragraph.
  3. Pressing 'Shift + Enter' should allow users to continue the quote on a new line.
  4. Selecting 'Paragraph' should convert the quote to a paragraph without removing the text.
Reproduce Steps
  1. Open Rules V3 using TinaCMS.
  2. Start editing a rule.
  3. Click on 'Quote' to begin a quote.
  4. Type some text and attempt to end the quote using 'Enter' or 'Shift + Enter'.
  5. Observe that the quote continues or is removed entirely.
Screenshot

Screenshot
Figure: No way to end quote without removing it

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the quote behavior in Rules V3 using TinaCMS, following the listed steps and the linked video. Inspect the TinaCMS editor configuration and identify how Enter, Shift + Enter, and Paragraph currently handle quotes; done means each acceptance criterion works without losing text.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
content, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.