added a state to hold the current text being typed

[timea-solid]

Fixes the #843 bug

[Copilot]

⚠️ Not ready to approve

The new localInputValue lifecycle currently risks rendering the input blank/stale due to being cleared and then always preferred by the render selection logic.

Pull request overview

This PR addresses issue #843 (“input typing is faster than saving of value”) by introducing a local, reactive state to keep the RDF input responsive while asynchronous store updates are in flight.

Changes:

• Added a @state()-backed localInputValue to decouple displayed input text from slower RDF store persistence.
• Updated render logic to prefer the local value while updates are in flight (or pending).
• Minor dependency lockfile update (electron-to-chromium patch bump).

File summaries

File	Description
src/components/rdf-input/RDFInput.ts	Adds local input state and integrates it into the render/update pipeline to prevent UI lag during async saves.
package-lock.json	Updates a transitive dev dependency version/integrity entry.

Review details

Comments suppressed due to low confidence (1)

src/components/rdf-input/RDFInput.ts:204

• Clearing localInputValue to '' immediately after a successful save can cause the input to briefly render empty while _updateInFlight is still true, and also interacts badly with the inputValue selection logic. It's safer to leave localInputValue as-is (it already holds what the user typed) and let the render logic decide when to fall back to the store value.

    try {
      await this.storeContext.store.updater.updateMany(toDeleteSt, toInsertSt as any)
      this.storeVersion += 1
      this.localInputValue = ''
    } catch (err) {

• Files reviewed: 1/2 changed files
• Comments generated: 1
• Review effort level: Low

Note

Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.