Forum https://discourse.hanamirb.org – Code of Conduct http://hanamirb.org/community/#code-of-conduct
[backend] [INFO] [2020-06-18 08:03:24 +0200] HTTP/1.0 GET 200 10.19.1.11, 10.10.10.95 /administration/items 18682 {"environment"=>"production", "from"=>"2020-06-16", "until"=>"2020-06-18"} 2020-06-17 23:06:55 +02002020-06-17 23:06:55 +0200?
+0200 part then it represents the timezone. I think this ones specifically: https://en.wikipedia.org/wiki/UTC%2B02:00
has_many relationship, not has_many through:
Hi there. What is a better way to work with mongodb in hanami? I found hanami-mongoid gem that implements mongoid-based repositories but the gem has not been updated for 15 months already.
Of course I can get rid off hanami models and repositories and use mongoid directly but then I have concerns why I can't use just sinatra
Time.now to a monotonic clock: rack/rack@743f29d
elapsed properly: now = Time.now
length = extract_content_length(header)
msg = Hash[
http: env[HTTP_VERSION],
verb: env[REQUEST_METHOD],
status: status.to_s[0..3],
ip: env[HTTP_X_FORWARDED_FOR] || env[REMOTE_ADDR],
path: env[SCRIPT_NAME] + env[PATH_INFO].to_s,
length: length,
params: extract_params(env),
elapsed: now - began_at #calculation fails
]
@seban This article goes into it slightly: https://medium.com/adhawk-engineering/designing-services-with-dry-rb-fe850f8dd4b7
But it doesn’t describe how you can handle various results in your controller by calling your interactor with a block:
interactor.call(params) do |m|
m.success do |user, msg|
flash[:notice] = msg
redirect_to routes.user_path(@user.id)
end
m.failure(:auth_error) do |user, msg|
flash[:notice] = msg
redirect_to routes.auth_error_path
end
m.failure do |user, msg|
flash[:notice] = msg
redirect_to new_session_path
end
endIt’s a really great way to handle interactor results, sorry I don’t have a more in-depth example for you but you could google around if you’re interested in using it.
I have a question.
hanami/model#294
How does everyone avoid creating anemic domain model ?
Although entities are the core of an application and should have methods related to domain logic, we can't add update method to them, because they are immutable objects.
In this article, he says that you should use repository for update process, but does it seem to be outflow of domain logic? ("anemic domain model")
I have a follow-up problem to my aggregate. The full gist is still here .
For the aggregate below I would like to filter by the translation_record's attribute as well. To get only records for a given language combination. I need this, because, as I stated before, the aliased self-relational association doesn't work yet in this version of Hanami Model.
class SegmentRepository < Hanami::Repository
associations do
has_many :translation_records
has_many :segments, through: :translation_records, as: :target_segments
belongs_to :language
end
def find_by_segment_match(source_text_for_lookup, source_lang, target_lang, sim_score, max_results)
aggregate(:translation_records)
.where {similarity(:content, source_text_for_lookup) > sim_score/100.00}
.select_append {float::similarity(:content, source_text_for_lookup).as(:similarity)}
.order {similarity(:content, source_text_for_lookup).desc}
.limit(max_results)
end
endI've added a language_combination attribute to translation_records.
I want to do something like .where {translation_records.language_combination = "#{source_lang}_#{target_lang}". This yields: undefined method meta for TranslationRecord:Class
@sebastjan-hribar
class UserRepository
associations do
has_many :posts
end
def find_with_posts_by_created_at(user_id, from: nil, by: nil)
aggregate(:posts)
.where(users[:id].qualified.is(id))
.node(:posts) do |posts|
posts.where(post_created_at_gt(from))
.where(post_created_at_lt(by))
.order(post_created_at_desc)
end
.map_to(User).one
end
private
def post_created_at_gt(from)
(posts[:created_at].qualified > DateTime.parse(from).to_time + 1)
end
def post_created_at_lt(by)
(posts[:created_at].qualified < DateTime.parse(by).to_time + 1)
end
def post_created_at_desc
posts[:created_at].qualified.desc
end
endDoes this code help you?
I found node method at rom-rb documentation.
https://api.rom-rb.org/rom/ROM/Relation/Combined#node-instance_method
This works great:
def find_by_segment_match(source_text_for_lookup, source_lang, target_lang, sim_score, max_results)
aggregate(:translation_records)
.node(:translation_records) do |translation_records|
translation_records.where(language_combination: "#{source_lang}_#{target_lang}")
end
.where {similarity(:content, source_text_for_lookup) > sim_score/100.00}
.select_append {float::similarity(:content, source_text_for_lookup).as(:similarity)}
.order {similarity(:content, source_text_for_lookup).desc}
end
