You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we'll use the binstubs for a pre-compilation task, like always generating some files, then let's simplify and document the bin files.
What do you mean around using binstubs for pre-compilation task?
Would proposed approach literally move the code in binstub to some shakapacker/binstub file? What's the use case and benefit of adding extra code there rather than to the current generated binstub?
If we use the binstubs for a pre-compilation task, like always generating some files, then let's simplify and document the bin files.
The point is to make the binstub as compact as possible so that any customizations can be identified more easily.
Current bin file https://github.com/shakacode/shakapacker/blob/main/lib/install/bin/shakapacker has:
How about something like that is easier to read and modify?
And the same for the https://github.com/shakacode/shakapacker/blob/main/lib/install/bin/shakapacker-dev-server
The text was updated successfully, but these errors were encountered: