-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Decaffeinate spec/spec-helper
(Merge first: it's a dependency)
#19
Conversation
You can remove the |
decaffeinate-project is used at first, then manual refactor/clean. |
Following @confused-Techie comment, I forgot to follow Decaffeination guidelines. Steps to reproduce decaffeination:
|
spec/spec-helper
spec/spec-helper
(Merge first: it's a dependency)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be merge 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR looks fantastic, and I really do appreciate you linking and informing us about how the guide was used @GuilleW.
Thanks a ton for the contribution! 🎉
I'll go ahead and leave this up for a small time longer to ensure any other members are able to take a look otherwise I'll go ahead and merge it
@confused-Techie Well well, it seems that the "small time" has passed. :) Unfortunately, though, it cannot be merged immediately, since it needs to be consolidated with later changes... My idea would be to collect all changes to these coffee files, since the last commit of this branch, and integrate them into the js code as well. There cannot be that many changes. I can help if you wish. |
Yeah I'm sorry about that. If it's any consolation, your collection of PRs here helped us determine our proper workflow for decaf PRs, due to the difficulty in accurately reviewing them. If willing any help would be awesome, but also if fine by you, I'd be willing to restructure these into our new workflow, so that they can finally be reviewed and merged. Essentially what we have been doing going forward for any decaf work is this: Firstly create a branch of only machine decaf files. That way we are able to review what you specifically have done, without caring at all about the actual decaf, since we know the machine decaf will work. Finally from there, once properly reviewed we can then merge it, but at the last second change the target branch to be the But again, sorry for how long these have sat here untouched, if you're willing seeing this as a PR would be amazing, or if it's fine by you, I could do this with your changes, and attribute you as the author on the PRs |
This doesn't sound too bad. One can create a new machine-decaf branch from the current state of things, and then merge the updated version of this PR to that. What still needs to be kept in mind is that the main branch still needs to kept frozen, from the generation of the machine-decaf to the eventual merging of it. I heard you had a discord server, let's talk about it there. |
Without further objections, this PR is superseded by #63. |
Helper for unit test.
⚠️ Should be removed at this end! ⚠️
PR needed before other decaffeination in spec, because this file is included.
I don't remove
spec/spec-helper.coffee
actually, because it's useful during decaffeination.