Search Ideas
2884 ideas match your query.:
Fixed as of 99b6280, to be released in version 1.6.0.
On Rails 8.1, Hiccdown's capture hands keyword arguments to the block as key-value pairs rather than as keywords. capture(text: 'foo') { |text:| text } raises ArgumentError: missing keyword: :text instead of returning 'foo', and a block that takes them as a hash, { |options| … }, gets [:text, 'foo'] instead of {text: 'foo'}.
Earlier versions of Rails pass keywords on to the block as a hash, which Hiccdown leaves alone.
Mostly, intercepting capture already took care of it: helpers of your own that pass a block on to Rails' helpers, or return Hiccdown, worked. Hiccdown given to Rails' helpers as content didn't, as in content_tag(:div, yield), tag.div([:span, 'foo']) or link_to([:span, 'foo'], path). As of 134deb9, to be released in version 1.6.0, it does.
Yes. As of 4fd7a0e, to be released in version 1.6.0, the layout named X lives in XHelper#layout, just as it would in layouts/X.html.erb, so the application layout lives in ApplicationHelper#layout. yield and yield(:title) work as in an ERB layout, and layout files keep working for a gradual migration.
Fixed as of 31cf174, to be released in version 1.6.0.
Fixed as of 9c46c61, to be released in version 1.6.0.
Hiccdown finds an action's helper method through params[:action] rather than the controller's action_name. When a controller runs without the router, as in ProductsController.action(:show).call(env), params[:action] is nil and rendering raises NoMethodError: undefined method 'to_sym' for nil instead of calling ProductsHelper#show.
Calling render with options only, such as render status: :not_found or render layout: 'admin', skips the action's helper method and looks for an ERB template instead. Without one, it raises ActionView::MissingTemplate:
class ProductsController < ApplicationControllerdef showrender status: :not_found # MissingTemplate, though ProductsHelper#show existsendend
Naming the action works around it: render :show, status: :not_found.
Rational Decision-Making
It’s rational to adopt only those ideas which, as written, don’t have pending criticisms, and to reject ideas that do.
If an idea, as written, has no pending criticisms, it’s rational to adopt it and irrational to reject it. What reason could you have to reject it? If it has no pending criticisms, then either no reasons to reject it (ie, criticisms) have been suggested or all suggested reasons have been addressed already.
If an idea, as written, does have pending criticisms, it’s irrational to adopt it and rational to reject it – by reference to those criticisms. What reason could you have to ignore the pending criticisms and adopt it anyway? After all, the previous paragraph applies to pending criticisms, too.
See also:
Rational Decision-Making
It is rational to adopt only those ideas which, as written, don’t have pending criticisms, and to reject ideas that do.
If an idea, as written, has no pending criticisms, it’s rational to adopt it and irrational to reject it. What reason could you have to reject it? If it has no pending criticisms, then either 1) no reasons to reject it (ie, criticisms) have been suggested or 2) all suggested reasons have been addressed already.
If an idea, as written, does have pending criticisms, it’s irrational to adopt it and rational to reject it – by reference to those criticisms. What reason could you have to ignore the pending criticisms and adopt it anyway? After all, the previous paragraph applies to pending criticisms.
See also:
A sticky button can't work here: the main content area has to be a horizontal scroll container so deeply nested trees can grow sideways, and that stops position: sticky from sticking. The workarounds (reworking the global layout, or JavaScript positioning that jitters on mobile) are too risky for such a small benefit.
Tyler suggested (#3904) we use the chart type from Kialo:
Could be a useful visualization in addition to trees.
Each top-level idea would be the center node. Then red segments around it for pending criticisms. Gray for non-pending criticisms and neutral comments.
Unlike Kialo, though, each segment would have the same size as the other segments on its circle.
Offer easy way to link to latest version of an idea. The ability already exists – an idea link + /latest will always go to the latest version – but isn’t directly exposed in the form of a link or button yet.
Reiterating/refining #3904: There should be a graphical indication for pending criticisms. The dropdown line should be red if the comment it leads to is a pending criticism. The yellow pills can be turned gray to be easier on the eyes.
This says nothing about the yellow color of the criticisms pills, which I think Tyler is saying are too harsh on the eyes.
That doesn’t mean the pill has to stay yellow. Too harsh.
That doesn’t mean the pill has to say yellow. Too harsh.
And dimmer red for refuted criticisms, brighter red for pending ones! Default gray for comments.
Would get alternating dim and bright depending on insertion order. Confusing!
Reiterating/refining #3904: There should be a graphical indication for pending criticisms. The dropdown line should be red if the comment it leads to is a pending criticism.
Reiterating/refining #3904: I think the yellow "Criticism of" bubbles can and should be replaced by a graphical indication that is much easier on the eyes. The dropdown line can be made red if the comment it leads to is a criticism, and the bubble on the criticism can be eliminated. Reading the yellow bubble to get the idea # it is referring to, then searching the ideas above for the matching # is inelegant (even if it is usually the one right above).
And dimmer red for refuted criticisms, brighter red for pending ones! Default gray for comments.
It’s more in line with refute.us if non-pending criticisms are neutralized, ie gray as well.