Skip to content

[WIP] Fix Opal runtime compatibility for adapter loading#649

Draft
suleman-uzair wants to merge 3 commits intofix/global-context-register-lookup-fallbackfrom
fix/opal-runtime-compatibility
Draft

[WIP] Fix Opal runtime compatibility for adapter loading#649
suleman-uzair wants to merge 3 commits intofix/global-context-register-lookup-fallbackfrom
fix/opal-runtime-compatibility

Conversation

@suleman-uzair
Copy link
Copy Markdown
Member

Summary

Adds runtime compatibility handling so adapter, schema, and XML serialization loading work correctly under Opal.

Changes

  • Adds shared runtime helpers for Opal/native checks, native-only requires/autoloads, and safe constant lookup.
  • Uses Opal-safe load paths for key-value and XML adapters.
  • Avoids native-only TOML adapter defaults in Opal.
  • Ensures XML serialization/import methods are applied directly to Serializable under Opal.
  • Keeps Nokogiri-specific entity handling limited to native XML parsing paths.

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