refactor for backstop-core implementation
See original GitHub issuegulp.run()
was used in the initial implementation of BackstopJS and is now deprecated. It’s time we go back and straighten out these logic issues in a more Gulp-friendly (platform-agnostic) way. Any assistance on this refactor is greatly appreciated!
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Code Refactoring Best Practices: When (and When Not) to Do It
Code refactoring is a process used in the DevOps philosophy that involves editing and cleaning up ... [GREEN]; Implement improvements.
Read more >Refactoring Techniques
These refactoring techniques show how to safely move functionality between classes, create new classes, and hide implementation details from public access.
Read more >What is Refactoring (Code Refactoring)? - TechTarget
Refactoring can be performed after a product has been deployed, before adding updates and new features to existing code, or as a part...
Read more >7 Code Refactoring Techniques in Software Engineering
Firstly you gather some basic requirements and then based on the requirement you start implementing the feature one by one.
Read more >Advanced Topic - Refactoring - Scaled Agile Framework
Interface / Implementation – First, create new interfaces and wrap in the old functionality, then refactor the functionality itself.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@YuliaTsareva @garris I thought about this a couple of weeks ago as well. What I would love to do is to extract something like a
backstop-core
module. Thisbackstop-core
would basically consist of all components which are needed in order to run backstop and expose the needed functions as plain javascript-functions. Then we could do something likegulp-backstop
(or just call itbackstop
to make it backwards compatible) which is a gulp-wrapper for the functions (and dependencies) exposed by backstop-core. If we would need a CLI-runner we could create something likebackstop-cli
orbackstop-clite
I think this could also greatly benefit CI integration #135 and tools like grunt-backstop because they can just use the
backstop-core
part. And furthermore we would also avoid exposing internal tasks (likethe jscs-task
to our api (which are all tasks in the gulpfile).Closed by #259