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
However, dialyzer is complaining about the opacity of :bbmustache.template() being broken because it is matched against a pattern.
It would be nice if :bbmustache.template() weren't opaque. Better yet, it would be nice if :bbmustache.parse_option() allows get_partial_fun which defaults to the current implementation of reading the partial from a file.
I'd love to submit a PR but my Erlang skills are severely lacking.
The text was updated successfully, but these errors were encountered:
I understand your motivation and difficult to use local file I/O on many systems.
I think that it should keep bbmustache::template() is opaque, because bbmustache does not want to make any changes to the data structure externally.
If it changes, backward compatibility will be difficult.
It is a good policy to add an option to parse_option.
In our Elixir project, we couldn't save partials in the filesystem. To work around this, we wrapped
bbmustache
like so:However, dialyzer is complaining about the opacity of
:bbmustache.template()
being broken because it is matched against a pattern.It would be nice if
:bbmustache.template()
weren't opaque. Better yet, it would be nice if:bbmustache.parse_option()
allowsget_partial_fun
which defaults to the current implementation of reading the partial from a file.I'd love to submit a PR but my Erlang skills are severely lacking.
The text was updated successfully, but these errors were encountered: