We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I am trying to write a Tapioca compiler for pg_search.
The problem is that currently, there is no way to know which methods were generated by pg_search by introspecting an Active Record model class.
Ideally, pg_search would maintain a list of the methods generated by its pg_search_scope DSL. Rails itself does this for a variety of its DSLs.
pg_search_scope
For example: the scope DSL calls generate_relation_method, which keeps track of generated methods in the GeneratedRelationMethods module which can then be retrieved by calling the (private) method generated_relation_methods.
scope
generate_relation_method
GeneratedRelationMethods
generated_relation_methods
Would you be open to such a change? If so, I'd be happy to submit a prototype in a PR and discuss from there.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
I am trying to write a Tapioca compiler for pg_search.
The problem is that currently, there is no way to know which methods were generated by pg_search by introspecting an Active Record model class.
Ideally, pg_search would maintain a list of the methods generated by its
pg_search_scope
DSL. Rails itself does this for a variety of its DSLs.For example: the
scope
DSL callsgenerate_relation_method
, which keeps track of generated methods in theGeneratedRelationMethods
module which can then be retrieved by calling the (private) methodgenerated_relation_methods
.Would you be open to such a change? If so, I'd be happy to submit a prototype in a PR and discuss from there.
The text was updated successfully, but these errors were encountered: