![class Meaning < ActiveRecord::Base
has_many :senses
AS_JSON = {
only: [:id, :name],
methods: [:voiceover_url],
include: {senses: Sense::AS_JSON}
}
AS_JSON_SHORT = {only: [:id, :name]}
def as_json(opts = {})
super opts.merge(opts.delete(:short) ? AS_JSON_SHORT : AS_JSON)
end
end
# controller
def index
render(json: collection.to_json(short: true))
end](https://image.slidesharecdn.com/rails-missing-features-130114131551-phpapp01/85/Rails-missing-features-45-320.jpg)
Uploaded byAstrails
Rails missing features
The document discusses various missing features and considerations in Ruby on Rails development, emphasizing the importance of community and decision-making. It mentions several content management systems (CMS) and libraries that can be used to enhance Rails applications, and highlights practices for JSON serialization, user authentication, and real-time web server communication. The author suggests focusing on simplifying frameworks to improve developer productivity and reduce decision fatigue.
More Related Content
![[.Net开发交流会][2010.06.19]better framework better life(吕国宁)](https://cdn.slidesharecdn.com/ss_thumbnails/net2010-06-19betterframeworkbetterlife-101007223326-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Rails missing features
- 1. Rails Missing Features We don't have all the answers but we definitely have some questions. Boris Nadion @borisnadion
- 2. Boris Nadion developing softwaresince early 90th working with Rails since 2005 partner at Astrails
- 3.
- 4.
- 5.
- 6.
- 7. community the best developerscommunity in the world
- 8. high quality code the community usually produces
- 9.
- 10. saves time not makingthe same decisions over and over again
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20. “static” pages Privacy Policy,Terms of Services, About Us, etc
- 21. not static atall customers what to change them from time to time
- 22.
- 23. basic CMS not afull featured monster
- 24.
- 25. High Voltage Rails Engine for static pages https://github.com/thoughtbot/high_voltage
- 26. Refinery CMS An opensource Ruby on Rails content management system https://github.com/refinery/refinerycms
- 27. BrowserCMS Humane Content Management for Rails https://github.com/browsermedia/browsercms
- 28. ComfortableMexicanSofa Rails 3 CMS Engine https://github.com/comfy/comfortable-mexican-sofa
- 29. another ~20 projects worth mentioning
- 30. it shouldn’t bea part of the framework!
- 31.
- 32.
- 33.
- 34. choice ERB is adefault
- 35. i18n keeps the textsin separate YAML files
- 36.
- 37.
- 38.
- 39. server: http://api.service.com AJAX calls client: http://example.com
- 40.
- 41. Rack CORS Middleware https://github.com/cyu/rack-cors
- 42.
- 43. business logic should be in a model
- 44.
- 45. class Meaning <ActiveRecord::Base has_many :senses AS_JSON = { only: [:id, :name], methods: [:voiceover_url], include: {senses: Sense::AS_JSON} } AS_JSON_SHORT = {only: [:id, :name]} def as_json(opts = {}) super opts.merge(opts.delete(:short) ? AS_JSON_SHORT : AS_JSON) end end # controller def index render(json: collection.to_json(short: true)) end
- 46. representation should be in a view
- 47.
- 48.
- 49. class MeaningsController <InheritedResources::Base respond_to :json actions :index end # app/views/meanings/index.json.json_builder meanings collection do |meaning| id meaning.id name meaning.name end
- 50.
- 51.
- 52.
- 53.
- 54.
- 55. real time web server push
- 56.
- 57. dumb server no businesslogic, no persistence, direct relay
- 58. notify push server Rails push server create/update content send updates client client client client client client
- 59. hosted solutions pusher, pubnub,hydna, and others
- 60.
- 61. pubnub = Pubnub.new(...keys and auth...) pubnub.publish( message: "some-message, preferably JSON", channel: "some-channel-name, preferably secret token" ) # somewhere on a client side ... PUBNUB.subscribe({ channel : "some-channel-name, preferably secret token", callback : function(message) { console.log("we've got a message", JSON.parse(message)) } });
- 62. config.push = :pubnub config.push_auth= {...} Rails.push.publish(channel: @post.token, json: @comment) # somewhere on a client side ... $(window).on("push", function(e, channel_name, message) { console.log("new message", channel_name, message); });
- 63.
- 64.
- 65.
- 66.
- 67. a part ofthe framework
- 68. save a lotof time to spend it on...
- 70.
- 71.
- 72. Thank you! Slides andvideo will be published at http://astrails.com/blog Boris Nadion @borisnadion