-
Notifications
You must be signed in to change notification settings - Fork 20
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
removeSegment? #5
Comments
Good observation James. I felt it was a little dangerous to add/define I think that it would be safer to define a However, I think you do make a good point regarding the removal of a segment based on another expression and I think a good example would an OR with a look ahead... it might also help with the Feel free to add me on google plus (selvin@selvin.co) and maybe we ca talk about this in a hangout or something if you have some ideas you'd like to share. |
- Adds getSegments() to improve testability [Issue #5](#5) - Adds composer package [selvinortiz/flux](https://packagist.org/packages/selvinortiz/flux) - Adds dev branch - Adds contributing notes - Adds install notes
- Adds getSegments() which was not included in 0.5.0 [Issue #5](#5) - Adds removeSegment() which can be used in unit tests as well - Adds lineBreak() and br() which matches a new line (DOS/Unix) - Adds clear() which allows you to clear out the pattern and start from scratch - Adds getPattern() which compiles the expression and returns it - Adds deprecation candidates as @todos - Fixes mixed logic between add() and raw() - Fixes implementation on the orTry() method - Moves example in readme above changelog - Improves unit tests
Flux 0.5.1 is now ported to node-flux |
@jbrooksuk Awesome James 👍 |
Since you can
getSegment
, would it be worth being able toremoveSegment
? It'd only be used really when running tests or maybe changing your regex based on a later condition.The text was updated successfully, but these errors were encountered: