The second argument of the route method is where we'd add route parameters! So, if you need a route for:

router.post('/movies/:id/activate', [MoviesController, 'activate']).as('movies.activate')

  

    

      Copied!
      

        

      
    
  
  
    
    
    
    
    
  

You could use the route method in EdgeJS to generate it like so:

<a href="{{ route('movies.activate', { id: 1 }) }}">
  Activate
</a>

  

    

      Copied!
      

        

      
    
  
  
    
    
    
    
    
  

The third argument is then additional config options, which includes qs to add to the URLs query string. So, there are other options you can include beyond qs to the third argument. Alternatives to this would include, as you've discovered, hard coding the query string outside the route method. You could also use the Route Builder, I believe you'd need to add this as a global to EdgeJS as I don't think it is included out of the box. However, the Route Builder would be AdonisJS solution to your second example!

What I normally do, though, is wrap the route helper in my own service to make things super easy to read! For example, a usage of my form service would be:

<form method="POST" action="{{ form.delete('redis.flush') }}">
</form>

  

    

      Copied!
      

        

      
    
  
  
    
    
    
    
    
  

You could also create EdgeJS components for this as well, which I've done in the past so you could do:

@form.delete({ action: route('redis.flush') })
@end

  

    

      Copied!