-
Notifications
You must be signed in to change notification settings - Fork 2
Current state of Metafix implementation #60
Conversation
Starting from a record map, not the event-based morph classes Following Catmandu Fix cheat sheet at https://github.com/LibreCat/Catmandu/wiki/Fixes-Cheat-Sheet
MetafixFilter was removed in f328a13
And TODOs for internal record representation as JSON-equivalent
Flattened field names vs. actual entities, both for emitting and internal representation (apply actual JsonPath to the record?)
WIP: 4 failing tests with TODO comments for missing entity support
WIP: 3 failing tests with TODO comments for missing entity support
WIP: 2 failing tests with TODO comments for missing entity support
Used in `if` statements with `(all|any|none)_(contain|equal|match)`
Access group by name instead of index (which may be off when used in combination with unnamed groups).
Accidentally deleted during refactoring in a786f73
Hm, that must have happened accidentally during refactoring, I restored them in e4dec3a.
Right, that should have been a separate commit, but was intentionally. My idea was that we don't need a separate filter command with fix, since we can filter in the main fix (or in a separate fix, but with normal fix behavior), e.g. like this. |
Yes, good point. I opened #64 for that. |
Agreed, |
@blackwinter Alright, I hope I have addressed or opened issues for all your points. Reassigning & re-requesting review. |
Yes, I believe everything's been addressed. Thank you! 😄 Once the conversation regarding the binding scope in |
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.
OK, let's move on then :)
For consistency: org.metafacture:metamorph org.metafacture:metafix
org.metafacture.fix/src/main/java/org/metafacture/metafix/FixMethod.java
Show resolved
Hide resolved
Seems to be currently unused and doesn't do what it's supposed to do. See #60 (comment).
Seems to be currently unused and doesn't do what it's supposed to do. See #60 (comment).
As discussed in our recent meeting, we want to merge the current state of the Metafix implementation into the main branch to make clear where the main development is happening.
Would it make sense to resolve #35 with this and open new issues for specific improvements / new features?
@blackwinter Feel free to merge yourself as I'll be on vacation starting tomorrow (back on the 25th).