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

oset being strict

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure, javascript
Domain
tooling

Research direction

Start with the oset+ entry point and compare its behavior with the working gobj/set call on the same doc, todos, index, and done values. Trace how oset+ performs the nested update and verify the fix against the reported Automerge case, ensuring direct oops access no longer produces the writable=false browser error.

Written by the indexing model from the issue text.

Description

Hello,

I'm trying to use oops to interop with Automerge.

This snippet fails to make an update:

(oset+ doc "todos" (str idx) "done" true)

The browser complaints that: data property descriptor has writable=false

But if I try something a bit different:

(gobj/set (oget+ doc "todos" (str idx)) "done" done)

This works just fine, the google impl is a single obj[key] = value. I wonder if there is a way to make oops work directly without having to fall back into Closure helpers.

Dominant language
Clojure
Stars
350
Forks
13
PR merge metrics
No merged PRs in 30d

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.

More from binaryage/cljs-oops

All issues in binaryage/cljs-oops

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.