Skip to content

Support GitHub reviews with ghub 5.1 - #10

Open
ArthurHeymans wants to merge 1 commit into
doomelpa:masterfrom
ArthurHeymans:GhubLegacy
Open

Support GitHub reviews with ghub 5.1#10
ArthurHeymans wants to merge 1 commit into
doomelpa:masterfrom
ArthurHeymans:GhubLegacy

Conversation

@ArthurHeymans

Copy link
Copy Markdown

Ghub 5 moved the obsolete ghub-graphql helper out of ghub-graphql.el and
into ghub-legacy.el. Ghub 5.0 still loaded ghub-legacy from ghub.el, but
Ghub 5.1 stopped doing so, leaving code-review's GitHub metadata fetch
with (void-function ghub-graphql).

Load ghub-legacy only when ghub-graphql is not already defined. This
keeps compatibility with older ghub releases that still provide
ghub-graphql through (require 'ghub), while restoring compatibility with
newer ghub releases where the legacy wrapper must be loaded explicitly.

Signed-off-by: Arthur Heymans arthur@aheymans.xyz

Ghub 5 moved the obsolete ghub-graphql helper out of ghub-graphql.el and
into ghub-legacy.el. Ghub 5.0 still loaded ghub-legacy from ghub.el, but
Ghub 5.1 stopped doing so, leaving code-review's GitHub metadata fetch
with (void-function ghub-graphql).

Load ghub-legacy only when ghub-graphql is not already defined. This
keeps compatibility with older ghub releases that still provide
ghub-graphql through (require 'ghub), while restoring compatibility with
newer ghub releases where the legacy wrapper must be loaded explicitly.

Signed-off-by: Arthur Heymans <arthur@aheymans.xyz>
ykoor pushed a commit to ykoor/code-review that referenced this pull request Aug 7, 2026
…elpa#5, doomelpa#7)

- doomelpa#10: load ghub-legacy when ghub-graphql is not already defined,
  restoring compatibility with ghub 5.1 while keeping older releases
  working.
- doomelpa#8 and doomelpa#5: fix the payload structure in code-review-send-labels
  (vector of label names, correct post/put choice).
- doomelpa#7 (amended): instead of advising closql--abbrev-class, advise
  closql--coerce and closql--remake-instance to replicate closql
  2.4.0's Emacs 30 handling of EIEIO records.  The original advice
  only covered one call site of the same root cause.  Verified on
  Emacs 30.2 with closql 2.3.2 and 2.4.1, with
  eieio-backward-compatibility both enabled and disabled.
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.

1 participant