Skip to content

Fix issue with repeat schema registration#27

Merged
Silarn merged 1 commit into
masterfrom
bug/registration-fix
May 9, 2026
Merged

Fix issue with repeat schema registration#27
Silarn merged 1 commit into
masterfrom
bug/registration-fix

Conversation

@Silarn

@Silarn Silarn commented May 9, 2026

Copy link
Copy Markdown
Member
  • After first schema registration, storage is always set
  • On subsequent registrations, the registry registration was skipped due to the storage not being null
  • This should fix the storage check and allow all schemas to register properly

- After first schema registration, storage is always set
- On subsequent registrations, the registry registration was skipped due to the storage not being null
- This should fix the storage check and allow all schemas to register properly
@Silarn Silarn requested a review from Holt59 May 9, 2026 05:30

@Holt59 Holt59 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really understand the change but this seems to have fixed the issue so.

@Silarn

Silarn commented May 9, 2026

Copy link
Copy Markdown
Member Author

Removing the original if statement is the important part. The rest is just preventing the code from creating a new 'storage' class when one is already instantiated.

@Silarn Silarn merged commit 89a5662 into master May 9, 2026
4 checks passed
@Silarn Silarn deleted the bug/registration-fix branch May 15, 2026 06:48
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.

2 participants