Skip to content

Define app_issues resource - #51

Merged
shime merged 1 commit into
mainfrom
feature/ow-1364-define-app-issues-resource
Jul 16, 2026
Merged

Define app_issues resource#51
shime merged 1 commit into
mainfrom
feature/ow-1364-define-app-issues-resource

Conversation

@pbalaban

@pbalaban pbalaban commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Allow CRUD operations for App::Issue

@pbalaban pbalaban added review Please look at my code team-ow Operations & Workflow labels Jul 16, 2026
@pbalaban pbalaban removed the review Please look at my code label Jul 16, 2026
@shime
shime merged commit 49bd6db into main Jul 16, 2026
4 checks passed
@shime
shime deleted the feature/ow-1364-define-app-issues-resource branch July 16, 2026 12:57
shime added a commit that referenced this pull request Jul 16, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@shime shime mentioned this pull request Jul 16, 2026
shime added a commit that referenced this pull request Jul 16, 2026
Included since 2.0.0:

- Add the `app_issues` resource (CRUD for `App::Issue`) (#51)
- Fix: a to-one relationship serialized with `"data": null` (e.g. a
charge line's `item`, or an included `barcode` on a product without one)
now reads as nil, matching the present-with-null attribute semantics —
instead of the parser dropping the key and the read raising
`Booqable::MissingAttribute` (#50)

Originally opened as 2.0.1; renamed to 2.1.0 because #51 adds a resource
(a feature, per the 1.1.0/1.2.0 precedent). The branch name still says
`release/2.0.1` — cosmetic only, the tag comes from `version.rb`.

Unblocks [logistics#26](booqable/logistics#26),
which is temporarily git-pinned to the #50 SHA — once this ships, the
pin swaps back to the published gem.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-ow Operations & Workflow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants