Forum https://discourse.hanamirb.org – Code of Conduct http://hanamirb.org/community/#code-of-conduct
Thanks @kaikuchn I'm using named routes. This is it
get '/clients', to: 'clients#index', as: :clients_indexCan you think of anything else to check? It's more a theoretical question though as I think it should redirect using GET but I won't use it as redirection from 'destroy' action make sense only if a form is used for calling the deletion. Using a form for this seems weird and I ended up with AJAX hence don't need to redirect now. But that raised a question about a proper way of sending DELETE in Hanami. <form>, AJAX do we we have anything else which would look as nice as link_to for 'edit' and 'new' ?
flash[:error_m] = params.error_messages. puts flash[:error_m] works and I see all messages in the server output. The template has simply this code <%= flash[:error_m] %> and nothing renders.
Warning! Rack::Session::Cookie data size exceeds 4K.
Warning! Rack::Session::Cookie failed to save session. Content dropped.@kaikuchn no, just tested, seems it's definitely Hanami which is trying to do a redirect keeping the original HTTP method, i.e. DELETE in case of my destroy action.
This is the action code below, see I disabled halt and enabled redirect_to. Did not change anything else since I moved to AJAX for this, but the below is still OK for this test as only checking the log. clients_index_path route does work - tested separately with link_to
def call(params)
ClientRepository.new.delete(params[:id])
#halt 200
redirect_to routes.clients_index_path
endResult:
HTTP/1.1 DELETE 302 127.0.0.2 /admin/clients/8 5 {"id"=>"8"} 0.015793
HTTP/1.1 DELETE 405 127.0.0.2 /admin/clients - {} 0.007453
HTTP/1.1 GET 200 127.0.0.2 /admin/clients 1856 {} 0.016227The last line is my test of the route with GET. So definitely in case of HTTP DELETE, route_to tries to do a redirect using the same DELETE method. Obviously it is not supported by my routes and hence 405. Question - is it a bug or a feature? Anyway seems reasonable if redirect_to could always use GET or had an option to specify the method.
This is how to read those logs:
- Received DELETE Request using HTTP/1.1 from 127.0.0.2 for path /admin/clients/8, responded with 302 within 0.015793 seconds
- Received DELETE Request using HTTP/1.1 from 127.0.0.2 for path /admin/clients, responded with 405 within 0.007453 seconds
So you are sending two delete requests, why ever you are doing this. I'm pretty sure that it's not something Hanami is doing, like 99%. The third request you send is then the get request I'd expect after Hanami had send your client a redirect response. The 2nd request is weird.
self.body = XYZ only works in controller modules!
Object#inspect as an equivalent to the var_dump of php..? No clue what var_dump does though.
Maybe you could provide a minimal reproducible example? If you find the time and motivation to do so it would be much appreciated.
app folder but that without somehow embedding one or a few of these bundlers into hanami asset management capabilities ... I don't know, I really don't get the logic!
I think this was put there because at one point people wanted to work like that.. But I completely agree with you, I was never a fan of these repackaged js libraries that'd be always outdated and you didn't even get to use any of the goodness like google closure to reduce asset size.
For that matter I really don't like the asset pipeline approach at all, and I am very happy that the Ruby (on Rails) community has or is moving towards letting JS tooling handle JS.
Personally I only use Hanami for APIs (public or private, i.e., for frontends), so I have no clue what people do who go the classic route.
Slovenian.json localization file for DataTables (JQuery plugin) and how do I reference it during initialization?Currently, it's in my I18n folder under my app's Assets, but
"url": "../I18n/Slovenian.json" doesn't work. I've tried other variants, but can't get it to work. Any idea?
ArgumentError: +test?+ is not a valid predicate nameWhat am I doing wrong? Is there an easier way? I don't need to change or extend the logic, only want a local custom message
predicate :test?, message: 'Test' do |current|
return false
end
params do
required(:user).schema do
required(:key).filled(:test?)
end
endHas anyone any idea why this:
assert page.has_content?('some value'), "Page must have content some value."would succeed for show, but not for the update action? The spec is identical in that the before and after block are the same and I switch between
visit "/godmode/contacts/#{@contact.id}/edit" and visit "/godmode/contacts/#{@contact.id}" to compare what happens.
I can successfully puts all the text to the commandline via the spec and save_and_open_page shows all texts as well.
