features: add custom feature extraction framework - #305
Open
fippo wants to merge 1 commit into
Open
fippo wants to merge 1 commit into
fippo wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Sorry, something went wrong.
with a file `custom.js` that implements client, connection and track-based feature extraction with fields that are, by convention, returning features names start with `custom`. This maps to database fields with a `custom_` prefix and avoids collisions with standard features. Changes to custom.js will be rare so merge conflicts can be largely avoided
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
with a file custom.js that implements client, connection and track-based feature extraction with fields that are, by convention, returning features names start with custom. This maps to database fields with a custom_ prefix and avoids collisions with standard features.
Changes to custom.js will be rare so merge conflicts can be largely avoided