Skip to content
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

Proposed changes for ThirdRail compatibility #171

Closed
wants to merge 24 commits into from

Conversation

bglusman
Copy link
Contributor

@bglusman bglusman commented May 1, 2015

Hey @ryanstout thanks for your help today, though turned out not to be that and only to be my stupidity as usual.

Hopefully these changes are more or less acceptable as is, but let us know if you want any tweaks made, or if there's anything we need to rethink/rework significantly. Hopefully once this is merged in we can consider a third rail alpha release!

Thanks to @catmando and @pencilcheck, if either of you has any thoughts or suggestions speak up.

catmando and others added 20 commits March 22, 2015 21:58
Also, can't use ||= without setting default value
from Volt.root's internal @root ||=
Also, kill unneeded VOLT_PATH constant
Both seem like improvements though, and calling 
to_s lets us use symbols instead of strings 
if/when we get server side rendering to work
Server.index_files still feels like a hack/
bad idea, but can discuss in PR
third-rail is working for me without them in
any case, can discuss if they make sense anyway
We appear to be able to generate the files from
within third-rail, and if not a better/cleaner
interface than this would be preferable anyway
@@ -34,7 +34,7 @@ def connect!
var wsProto = 'ws';
}

this.socket = new WebSocket(wsProto + '://' + document.location.host + '/socket');
this.socket = new WebSocket(wsProto + '://' + document.location.host + '/volt/socket');
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not 100% sure this is needed, but seems like it would be with others.

@bglusman
Copy link
Contributor Author

bglusman commented May 1, 2015

Test failures are from namespace changes/prepending /volt to paths, which is one of the things I want to make sure you're OK with, but I'll fix specs for this assuming its OK

@ryanstout
Copy link
Member

Sorry, today was swamped, I'll check it out tomorrow. Thanks!

@bglusman
Copy link
Contributor Author

bglusman commented May 6, 2015

@ryanstout this keeps getting merge conflicts, I've fixed two, but don't want to bother fixing more until you've had a look at the general shape of changes and how close/far you are from being comfortable merging them. Maybe @catmando or @pencilcheck will weigh in or want additional changes too, don't know if you prefer to get it all in in one PR, or happy to have several.

@ryanstout
Copy link
Member

@bglusman sorry I've been so slow on this one. Can you move all of the method_defined checks into their own PR? I would rather not namespace all of volt by default. But I'm planning to add app name-spacing in by default so it can be embedded in another rack app anyway. So maybe we could pair sometime soon and knock that out?

@ryanstout
Copy link
Member

@bglusman did you see my last comment? I've got time if you want to try and get everything worked out and integrated.

@bglusman
Copy link
Contributor Author

Thanks Ryan, I saw and I've discussed a little in third rail room, think I
mostly understand but because latest version broke third rail completely,
and now we're contemplating breaking up these potentially incomplete
changes into smaller pull requests, I'm unsure whether to just hold off on
these, or merge in the lowest friction stuff to avoid as much surface area
for future conflicts. I'll try and come up with a proposal this week,
apologies for delay.

On Sunday, May 10, 2015, Ryan Stout notifications@github.com wrote:

@bglusman https://github.com/bglusman did you see my last comment? I've
got time if you want to try and get everything worked out and integrated.


Reply to this email directly or view it on GitHub
#171 (comment).

-Brian

Note: Sent from handheld, please excuse brevity, typos, transcription
errors, pocket dials, verbosity, ridiculousness, and other general inanity.

@ryanstout
Copy link
Member

@bglusman no problem. Yea, smaller PR's would be good. I've got a branch where I'm working on adding namespacing so you can just embed volt as a rack app. (Also trying to get rid of the $page global)

@bglusman
Copy link
Contributor Author

Awesome, you have a link to namespaces branch? Maybe I should branch off of
that or see if we can use that in place of some of these changes anyway.
Will have a look anyway, thanks!

On Sunday, May 10, 2015, Ryan Stout notifications@github.com wrote:

@bglusman https://github.com/bglusman no problem. Yea, smaller PR's
would be good. I've got a branch where I'm working on adding namespacing so
you can just embed volt as a rack app. (Also trying to get rid of the $page
global)


Reply to this email directly or view it on GitHub
#171 (comment).

-Brian

Note: Sent from handheld, please excuse brevity, typos, transcription
errors, pocket dials, verbosity, ridiculousness, and other general inanity.

@ryanstout
Copy link
Member

@bglusman its pretty early on that branch. Some of it has gotten merged recently.

@bglusman
Copy link
Contributor Author

Closing in favor of #210

@bglusman bglusman closed this May 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants