-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Equal sign as argument value #85
Comments
removed, wrong place! |
@martincox I close this issue as a fix is merged. Do you have any timeline for next release? |
Next release of riak? We have riak working under OTP20 now and work is currently underway to resolve various build issues and test suite failures. I'd anticipate that we should have a release candidate in around 3-6 months. Hopefully it will come together sooner, but I think realistically we're looking at closer towards the back end of the year. |
Next release of clique! :) |
By release, what do you mean? You mean a tag? Or something else (like a hex.pm release?) |
To fix vernemq/vernemq#740 a tag would be enough but a hex.pm release wouldn't hurt I guess. |
@martincox Can I help with anything to get the fix for this issue into an official clique release (version tag and/or hex.pm package)? |
I think I still have the power of tag. I'll try and DM the Martins today, if I get the go ahead I'll push a tag and let you know. I can't do the hex.pm stuff though. Alternatively, there is a set of community forked and managed projects at https://github.com/Kyorai/clique which has been pretty good at keeping release of minor deps going. You could speak to @Licenser about getting the latest clique out that way? |
I tried to use a equal sign (
=
) as value but it fails with:IMHO clique should pass down any additional equal sign as part of value. At least it should provide a way to escape them.
The text was updated successfully, but these errors were encountered: