-
Notifications
You must be signed in to change notification settings - Fork 166
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
[WIP] Pushing towards using Pathname consistently. Closes #216 #218
Conversation
Good stuff! Is there an easy way to detect where else this needs to happen? |
Not really, I follow the request chain, and keep an eye out for |
Tests are failing on
The error is raised when
Three basic ways of fixing this:
|
This option has my vote. I'd like to use |
I resolved the merge conflicts which arose because of #249. |
@dometto Did this end up in gollum-lib-5.x some way or other? |
Argh. No, looks like I accidentally deleted the branch on which this PR was based. I think we can restore it though. |
👍 |
Restored and also resolved a new merge conflict. You may have to recheck the Sorry for the messup! |
No worries, just glad my work still has a chance of being included in the next big release. ;) |
Just solved another merge conflict. Tests still fail, but that all seems to be due to some mistaken calls to
What needs to happen to |
Very cool. 👍
I don't remember to be honest. We would just have to hook up this gollum-lib code to gollum and see. |
Do we still want to get this into 5.x? |
No, I think we can release without. I'm keeping it open though for future reference. |
Related to #216. Note that while the gollum-lib specs pass, the gollum specs do not. Including these changes therefore requires changing gollum's code as well.