These are chat archives for opal/opal
@/all feedback request: gonna push a change to the sprockets pipeline that will require any root asset to have the
.opal_main extention, e.g. in a rails app
application.js.opal_main.rb. In addition I'm thinking about adding a list of paths that will be intrinsically marked as "main assets", something like:
Opal::Config.main_paths << 'application'in rails could be prefilled with the precompiler paths.
If anyone has better ext name to propose or see any drawback please let me know.
(this btw will greatly simplify the support for sprockets 4)
server.main = 'app'
.mainwould have made more sense
.orbas the file extension?
.mainbut the problem with that is that the extension must be registered to sprockets and root/main are just to specific, but maybe I can register it as a single ext… need to check
.rbyou can use
.opalwhich is still supported, personally I like
.js.rbto differentiate frontend files
.orblooks better and could be read as 'opal ruby'
.orbwere saying that this is OPAL ruby, not standard ruby
.opalmight make people wrongly assume that it's a different programing language altogether
.orblooks nicer than