René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"recognize json and json attribute type defaults","articleBody":"Currently `json` and `jsonb` rails record attribute types will work, except that the dummy value will not be initialized if the schema specifies a default type.  In other words lets say your migration specifies that a json column should have a default value of `{abc: 12}`.  The HyperModel behavior should load the dummy value while waiting for the server to return with `{abc: 12}`  instead it loads nil (which is an acceptable value for json and jsonb fields, so its nothing breaks.\r\n\r\nTo work around this include the following in some client-side file (at the beginning of `hyperstack/models/application_record.rb` works fine)\r\n\r\n```ruby\r\nmodule ReactiveRecord\r\n  class Base\r\n    class DummyValue \u003c BasicObject\r\n      alias build_default_value_for_jsonb build_default_value_for_nil\r\n      alias build_default_value_for_json build_default_value_for_nil\r\n    end\r\n  end\r\nend if RUBY_ENGINE == 'opal'  # the guard is important if its a file that is compiled server side!\r\n```\r\n","author":{"url":"https://github.com/catmando","@type":"Person","name":"catmando"},"datePublished":"2021-02-21T22:29:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/356/hyperstack/issues/356"}