DO NOT MERGE - Replace Wild Apricot lookup with deepharbor DHService#5
Draft
rubin110 wants to merge 1 commit into
Draft
DO NOT MERGE - Replace Wild Apricot lookup with deepharbor DHService#5rubin110 wants to merge 1 commit into
rubin110 wants to merge 1 commit into
Conversation
Point RFID scans at deepharbor's GET /v1/member/search_by_rfid_tag/ (OAuth2 password flow for the JWT) instead of Wild Apricot. Name precedence becomes nickname > first_name, and the printed label gains a pronouns line between the name and the optional subtitle. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Tested on the name tag printer. Works well. I've reverted the name tag printer to main after my test was complete.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was a test of having Claude Code on two different projects on two different machines work together to implement DH support in the nametag printer. This should not and must not be merged. I've only put it here to review.
Point RFID scans at deepharbor's GET /v1/member/search_by_rfid_tag/ (OAuth2 password flow for the JWT) instead of Wild Apricot. Name precedence becomes nickname > first_name, and the printed label gains a pronouns line between the name and the optional subtitle.