| // XPath CheatSheet | |
| // To test XPath in your Chrome Debugger: $x('/html/body') | |
| // http://www.jittuu.com/2012/2/14/Testing-XPath-In-Chrome/ | |
| // 0. XPath Examples. | |
| // More: http://xpath.alephzarro.com/content/cheatsheet.html | |
| '//hr[@class="edge" and position()=1]' // every first hr of 'edge' class |
forked from https://gist.github.com/chetan/1827484 which is from early 2012 and contains outdated information.
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
| { | |
| "theme": "light", | |
| "autoUpdate": false, | |
| "snippet": { | |
| "expanded": true, | |
| "newSnippetPrivate": false, | |
| "sorting": "updated_at", | |
| "sortingReverse": true | |
| }, | |
| "editor" : { |
rails new ror-app-name --api
This step is for creating a very basic level of model for us to work in. If you know already, or wish to apply your own custom models with relationships you can skip this step.
| # I submitted a bug report https://github.com/rails/rails/issues/34244 | |
| # b/c Rails was not honouring my `rescue_from` block which was causing my API to | |
| # be inconsistent. I was told this is expected behaviour. I think it's probably | |
| # fine for an HTML app where you control the form inputs. But for an API app, | |
| # the API is public facing and very important, so Rails shouldn't have its own | |
| # special errors that bypass my app's configuration and make my API inconsistent. | |
| # | |
| # Decided it shouldn't be too difficult to handle this myself. So, here is my | |
| # solution. It contains most of the important lessons I've learned about how to | |
| # get a Rails API app setup. It removes Rails' params parsing and adds its own. |
