Forum https://discourse.hanamirb.org – Code of Conduct http://hanamirb.org/community/#code-of-conduct
Ok, so this is the road map for hanami 2.0: https://trello.com/b/lFifnBti/hanami-20 You can follow @timriley's blog (https://timriley.info/) if you want to have a more detailed view on his personal progress with items from the road map. You can also check out his application template if you want to get started with hanami 2.0 now (https://github.com/timriley/hanami-2-application-template) he's using hanami 2.0 right now at the company he's working for, but warns that there's gonna be some degree of disruption. They do use it for 3 production apps though. But be warned, @parndt tried to get started and struggles with it a lot. He's promised to work on a getting started guide as a result of his struggles, but there is none yet!
People think that 2.0 is gonna be a 2021 Release but no promises. Stable versions of usable pieces may be released gradually, e.g. hanami-api or hanami-model.
Your continued interest has triggered the intent to finally write up a blog post about the status, goals, etc. probably with a Q&A, I'll let you folks know here when that happens. :)
I have a question about designing a REST API endpoint that would accept post requests.
We're building a middleware (call it M for brevity) that seats between a data provider (call it A) and data consumer (call it B). Here is the workflow:
- A user enters an ID in M and triggers the process.
- M calls A and gets the data.
- M sends the data to B.
- B uses the data to create an entity.
So the middleware might be used by a variety of B apps that all need to get the data from A. Due to constraints we need M and can't setup direct communication between A and B.
For the POC we need a test B app. My question is how to approach this. My high level picture is a REST endpoint in B that calls an interactor to create an entity. If this is correct, can someone help with some guidelines for the endpoint?
optional I guess? See Usage in this section of the guide https://guides.hanamirb.org/actions/parameters/#validations-coercion
optional escaped me, I'll try to forget I've asked as soon as possible :smile_cat: . As for calling another service synchronously I'll discuss it with the team, but I don't see any other option given the circumstances. Right now, error/exception handling seems our best bet. So, assuming we will do it, how should we go about it? Like I described above?
Hanami::Action::InvalidCSRFTokenError: Hanami::Action::InvalidCSRFTokenError after enabling sessions in application.rb. The secret is defined in the .env.development. This is the only thing that causes the error since after disabling the sessions again the app works with no errors.
So from what I gather I can either 1. pass the csrf token with the json request as per here or 2. override the verify_csrf_token? method as per here.
1: tried and it doesn't work, meaning the request doesn't go through. I also tried accessing the token explicitly with session[CSRF_TOKEN], but no success.
2: tried and it works, but I'm not sure if this approach is ok, well, safe.
Any other approach I missed?
hi guys,
I'm following this guide to upgrade hanami-validations to 2.0.alpha
But when running bundle update hanami hanami-vadidations, I got the error
Bundler could not find compatible versions for gem "dry-initializer":
In snapshot (Gemfile.lock):
dry-initializer (= 1.4.1)
In Gemfile:
hanami-validations (~> 2.0.alpha) was resolved to 2.0.0.alpha1, which depends on
dry-validation (~> 1.0) was resolved to 1.5.6, which depends on
dry-initializer (~> 3.0)
hanami-model (~> 1.3) was resolved to 1.3.2, which depends on
rom (~> 3.3, >= 3.3.3) was resolved to 3.3.3, which depends on
dry-initializer (~> 1.3)
Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.Seems like hanami-model and hanami-validations are using different version of dry-initializer. Can you guys kindly guide me through this please? TIA
Maybe this issue helps you
https://github.com/hanami/hanami/issues/1080#issuecomment-702755926
@thatguysimon You need to get to the router. I’m not saying this is the way you should do it, but playing around in the console I managed to iterate over the routes by doing this:
routes = Web.routes.instance_variable_get(:@routes)
router = routes.instance_variable_get(:@router)
router.routes.each { |r| puts r }There’s probably a more elegant way of getting there but you get the idea, you need to get to get to the Hanami::Routing::Route class, which has enumerator methods on it.
OpenStruct during runtime still invalidates method cache and/or impairs performance. i'm seeing newer blog post where ostruct is being used during runtime which makes me wonder if something changed.
