-
Notifications
You must be signed in to change notification settings - Fork 498
Add support for options #63
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
Conversation
|
I think the option to use a specific version of the compiler is a nice feature. What do you think, @axic? I would suggest |
|
@chriseth regarding your last comment, I initially kept the +soljson+ part initially to allow easy copy past from the version list. No strong opinion on that though. Could you please provide feedback and/or merge? |
New option to supply a custom compiler from the CLI Add very basic contract Move code out of the wrapper Add clean script Add some doc
|
@chevdor it would still be nice to merge your changes but they must be split up into bite sized chunks. If you are still interested, as a start could you create a PR which only contains |
|
Hi Alex
It has been a while. I need to see what is in those PRs. I see think it
would be great to have.
…On Mon, Feb 12, 2018, 11:46 Alex Beregszaszi ***@***.***> wrote:
@chevdor <https://github.com/chevdor> it would still be nice to merge
your changes but they must be split up into bite sized chunks.
If you are still interested, could you create a PR which *only contains*
solcjs-get?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAtFpGLezuDuS6xl1WL1YFFCmAZ-ZZD7ks5tUBaDgaJpZM4KeMnt>
.
|
|
hey guys, thank you for your wonderful work. are there anymore plans to include this? i would really really love to be able to specify compiler version on the cli cheers |
|
Thanks for the bump @tzapu |
|
thanks @chevdor for picking this right up /edit: i guess you can do it with this |
|
I don´t mind improving but I would only invest the time if some of the PRs I submitted years ago get merged. I created #227 to allow starting with smaller chunks and I would rather not grow the current PR too much right now as the reason it was not merged in the first place is probably the size. So I suggest focusing on #227 at first, once we have this one in, #63 will probably be easier to review as it mainly contains additional tests and doc. |
|
Ancient PR, not willing to fix conflicts once again. |
This is a rebased version of #55