Skip to content

Fix backward compatibility for old Rawilk namespace in settings keys#4

Merged
evan-burrell merged 2 commits intomainfrom
fix/backward-compatible-rawilk-namespace
Apr 2, 2026
Merged

Fix backward compatibility for old Rawilk namespace in settings keys#4
evan-burrell merged 2 commits intomainfrom
fix/backward-compatible-rawilk-namespace

Conversation

@evan-burrell
Copy link
Copy Markdown

Summary

  • Registers a class alias (Rawilk\Settings\Support\ContextAgentSoftware\Settings\Support\Context) in the service provider so old serialized data can still be unserialized
  • Modifies ContextSerializer::serialize() to normalize output to the old Rawilk namespace, ensuring generated keys match existing database entries
  • Works transparently for all key generator types (Readable, Md5, Hash) — no data migration needed

Test plan

  • All 179 existing tests pass
  • New tests verify serialized output contains old namespace
  • New tests verify old serialized data can be unserialized back to a valid Context
  • Verify against a real database with old Rawilk-namespaced keys

evan-burrell and others added 2 commits April 2, 2026 09:18
… namespace

The package rebrand from Rawilk to AgentSoftware changed the FQCN embedded
in serialized Context objects, breaking key lookup for existing database
entries. The ContextSerializer now normalizes its output to use the old
namespace, and a class alias is registered so old serialized data can still
be unserialized.
@evan-burrell evan-burrell merged commit d7cdcba into main Apr 2, 2026
@evan-burrell evan-burrell deleted the fix/backward-compatible-rawilk-namespace branch April 2, 2026 08:33
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.

4 participants