René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"The active model `where` method should act as a normal parameterized scope","articleBody":"Currently returns nil if used on a AR class, and throws a non-related error if used on a scope.\r\n\r\n\r\nTHIS WAS THE ORIGINAL CONCLUSION BUT ITS INCORRECT SEE DISCUSSION: \r\n\u003e The reasons we won't implement where is that it could be used to insecurely determine counts on data.  \r\nFor example `Customers.where(top_secret_attribute: true).count` could be executed from the JS console to find the count of customers with the top_secret_attribute.\r\n\r\n`where` should be implemented as a scope.   \r\n\r\nWe will need to add scope called `__hyperstack_internal_where_scope` \r\n\r\n```ruby\r\nclass ActiveRecord::Base \r\n  scope __hyperstack_internal_where_scope, \r\n    -\u003e(attrs) { where(attrs) }, # server side we just call where\r\n    filter: -\u003e(attrs) { !attrs.detect { |k, v| self[k] != v } # client side optimization\r\n  def self.where(attrs) \r\n    __hyperstack_internal_where_scope(attrs)\r\n  end if RUBY_ENGINE == 'opal'\r\nend\r\n```\r\n\r\nOn the client side we can add the class level `where` method to `ActiveRecord::Base` and which simpy calls the `__hyperstack_internal_where_scope.\r\n\r\n","author":{"url":"https://github.com/catmando","@type":"Person","name":"catmando"},"datePublished":"2019-01-28T16:43:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/116/hyperstack/issues/116"}