-
Notifications
You must be signed in to change notification settings - Fork 31
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
OpenRefactory JSON protocol documentation is missing #35
Comments
I have the document. I had started converting it to markdown to include in the repo but got distracted... Will finish and open a PR.
- Robert
… On Jan 15, 2017, at 11:01 AM, Jeff Overbey ***@***.***> wrote:
Line 74 of INTERNALS says: "The OpenRefactory protocol is documented at FIXME: URL"
It would probably be best to add it to the repository, probably under engine/protocol (since that's where it's needed).
IIRC, there's a Word doc and a PDF. No harm in uploading both.
@roberthorn do you have this document? If not, I'm sure I do somewhere... have to search...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Oh yeah, I think you told me you were doing that and I completely forgot. Awesome; thanks! |
Old thread, sorry for reviving it. {"command":"open", "version":0.1}
{"command":"setdir","mode":"web"}
{"command":"put","filename":"-.go","content":"package main\n\nimport \"fmt\"\n\nfunc main() {\n .... "}
{"command":"xrun","transformation":"rename","mode":"text","textselection":{"filename":"-.go","offset":114,"length":0},"arguments":["bar"]} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Line 74 of INTERNALS says: "The OpenRefactory protocol is documented at FIXME: URL"
It would probably be best to add it to the repository, probably under engine/protocol (since that's where it's needed).
IIRC, there's a Word doc and a PDF. No harm in uploading both.
@roberthorn do you have this document? If not, I'm sure I do somewhere... have to search...
The text was updated successfully, but these errors were encountered: