Luke Towers
Luke Towers
@bennothommo I asked for this issue to be opened, there were some ideas for this that I wanted to try but Sam was never interested in.
Mostly centred around using path resolving to ensures that the files existed in the themes directory, could also have it locked behind a config option like restrictBaseDir
I don't really understand what this PR is seeking to solve
Are you able to add a test case for this change?
To be honest I'd prefer we move away from supporting ambiguous aliases entirely.
@bennothommo further thoughts from @jaxwilko and myself regarding the potential for a "version replacement / management system" for individual files. We could provide the ability to upload new versions of...
Fair enough re: having the functionality as a plugin. That would probably work better for the company's interests anyways as the feature is a selling point with the existing product.
@WebVPF I appreciate the help; however I was thinking of making it easier to deal with client side translations in Winter CMS in general. One idea I was thinking up...
Personally I still like the idea of compiling the language files, support for the project level overriding of language strings is easily achieved by calling `Lang::get($groupCode)` rather than loading the...
I'm talking about generating a file somewhere and loading that in a link tag yes. We could potentially look at leveraging the Asset Compiler functionality to add support for loading...