Skip to content

fix: clone field resolver bug#254

Open
jasonbahl wants to merge 2 commits intodevelopfrom
fix/250-clone-field-bug
Open

fix: clone field resolver bug#254
jasonbahl wants to merge 2 commits intodevelopfrom
fix/250-clone-field-bug

Conversation

@jasonbahl
Copy link
Copy Markdown
Contributor

What does this implement/fix? Explain your changes.

This fixes (or at least attempts to 🤞) a bug where clone fields were not resolving properly.

Need more thorough testing but I'm having good luck with these changes.

Does this close any currently open issues?

closes #250

Any other comments?

Before:

Schema failed to load:

CleanShot 2025-04-07 at 14 47 15

After:

CleanShot 2025-04-07 at 14 46 02

Schema loads and fields can be queried as expected

- modify how data is passed down from group fields
- modify how field keys are mapped for groups where clone field keys are also passed down
@jasonbahl jasonbahl closed this Feb 11, 2026
@jasonbahl jasonbahl reopened this Feb 11, 2026
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.

Clone field problems, fields return null

1 participant