In 6, it looks like HTTPContext is a type, not an interface, so we can't just extend it that way, right?

The adonis 6 docs talk about extending httpcontext through macros and getters. Does that mean we can't just add a property like you do here? Also, contracts are out now, can I just add that interface definition in my app types file? I want to put together an object of properties I need throughout a request and add it to httpcontext. I was thinking of doing it in the route stack middleware. As usual, their documentation only explains about half of what you need to know so I am confused. You explain all this shit way better than they do.

Ok, so the return earlier is just passing on to the next validator, and unless you have that field.report() method, you are good. Thanks, that makes sense.

Are you going to do anything with form validation? I'm trying to write a custom rule for Vine and the docs don't seem to say what the function should return. In Laravel a validation function returned true or false but I cannot figure it out from the example they use in the Vine docs.

Ok thanks. That might do what I want just as well.

Hi Tom!

I'm trying to inject the context into a controller, and it is not working:

import type { HttpContext } from '@adonisjs/core/http'
import { inject } from '@adonisjs/core'

@inject()
export default class JoinController {
  ctx: HttpContext

  constructor(ctx: HttpContext) {
    this.ctx = ctx
  }
}

I got this error message:

Cannot inject "[Function: Object]" in "[class JoinController]

Sorry about the massive font lol. It looks like in the docs but does not work. Any ideas?

The URL builder in Adonis works fine, so I generate the route strings in my publish service and put the strings in the Edge template. Works great. Thanks!

which Queen City is yours? Cincinnati?

I want more! With a rebel yell, I cry "More! More! More!"

:)

Good stuff!

Thanks, I will check it out. I thought I had found the answer (I found "URL Builder" in the docs) but it still won't look up the routes inside Edge. And one clarification: I'm not doing subdomains, I'm doing different domains. It works fine on the routing end - everything routes correctly - but it's just inside Edge that it won't work. I will look at what you did and can probably kitbash it to my usage. I really appreciate all your time. You're a mensch.

Just FYI, this is how I generate the routes in my routes.ts file:

for (let site in Sites) {
 router
  .group(() => {
    router.get('/welcome/:tab?', [WelcomeController, 'welcome']).as('welcome')
    router.get('/join', [JoinController, 'join']).as('join')
    router.get('/upgrade', [JoinController, 'upgrade']).as('upgrade')
    router.resource('users', UsersController).as('users')
  })
  .domain(Sites[site].domain)
  .as(site)
}

So this still is not working. I tried it just like that, console.log confirmed it, and it still says it "cannot look up" the route.

How can I recreate the route outside of an Edge template? I don't see a helper for that. Laravel had a route helper you could use anywhere in the app to craft a url string. If I had that I could just craft the string in the service and feed it into Edge. Failing that, I will just have to manually create the URL strings. I can, but for all the reasons you know, would rather not.

Thanks for all your help.

Wow thanks. I did not get that from the documentation anywhere. Hey, question: Do you know of any full-featured V6 example site on Github? It would be soooo helpful to see a full example of all this stuff, service providers, the container, everything.

I should probably add that the 'moms' at the start of that route name is for a domain:

router
  .group(() => {
    router.get('/join', [JoinController, 'join']).as('join')
  })
  .domain('moms.test')
  .as('moms')

Hi, I am getting the Cannot lookup rote Edge error when I try to use an edge template with the route() helper in it.

      Error: Cannot lookup route "moms.join"
          at anonymous (D:\www\seeds\resources\views\moms\pages\home.edge:95:0)
<a class='button' href="{{ route('moms.join') }}">

That route shows up in list:routes:
GET /join (moms.join) .................................................. #controllers/join_controller.join

What am I doing wrong? Please let me know what additional information is needed.

Thank you.

Thanks! I followed the link to the source code and it looks like all I have to do to get what I want is request.hostname(), and that method just pulls the info out of the headers anyway.

Hi Tom, can you tell me why when I inspect the request object the parsed url host, protocol, etc are always null? I'm not sure the difference between host and hostname (if they were not null I could figure it out haha), but I want to be able to key off of that value in my code. I could grab the host header and parse that, but I'd rather just use the parsedUrl property for everything.

  "parsedUrl": {
    "protocol": null,
    "slashes": null,
    "auth": null,
    "host": null,
    "port": null,
    "hostname": null,
    "hash": null,
    "search": null,
    "query": null,
    "pathname": '/welcome',
    "path": '/welcome',
    "href": '/welcome'

Yup, that was it. I commented out the domain() and it works. Haha sorry about the wild chicken chase!

Oh hell, I think I know the problem and it has nothing to do with the import being hoisted. These routes are prefixed by a domain and I am not browsing to the domain. Duh!

Thanks again. It's weird that the routes show up when you run the ace command, but not in the app. I will try the function solution from your video and see if we get the same issue.

edit: I see what you did in your last comment. You made it dynamic instead of hard-coded like in the tutorial. Ok, I will try the comment approach.

console.log('Hello World!')

  

    

      Copied!
      

        

      
    
  
  
    
    
    
    
    
  

So I am getting "Exception Cannot GET:" in the browser on all of my routes. It points to node_modules/send/index.js

debug('stat "%s"', path)

fs.stat(path, function onstat (err, stat) {

if (err && err.code === 'ENOENT' && !extname(path) && path[path.length - 1] !== sep) {

// not found, check extensions

return next(err)

}

if (err)

return self.onStatError(err)

if (stat.isDirectory())

return self.redirect(path)

self.emit('file', path, stat)

self.send(path, stat)

Sorry, I don't know how to make it format code in these comment editors. Earlier it just did it automatically.

I see what you did there. I will give that a try and report back! lol Thanks

…. It worked! I have routes!

I guess it didn't work. Server did not throw an error but list:routes does not show any routes. Back to the drawing board!

Yeah, I used the functions on an earlier test and it worked great. Probably easier but I'm trying to learn the whole module imports thing so I wanted to try it this way. I made a subdir routes off of start and this is what I did. It appears to be working (didn't throw an error). Thanks!

import router from '@adonisjs/core/services/router'
import { fsReadAll } from '@adonisjs/core/helpers' 
const files = await fsReadAll(new URL('./routes', import.meta.url), { pathType: 'url' }) 
console.log(files) 
const imps: string[] = files.map((el) => { return el.substring(el.lastIndexOf('/') + 1, el.lastIndexOf('.')) }) 
console.log(imps) 
router.group(async () => { 
for (let domain of imps) { 
await import(`./routes/${domain}.js`) 
} 
})


  

    

      Copied!
      

        

      
    
  
  
    
    
    
    
    
  

Yeah, absolutely, I can imagine. I'm sure you are trying to crank out a million now to get people up to speed with Adonis 6. Must be crazy with all the changes they made. My below comment was because I'm trying to figure out for myself how to make these Adonis 5 tutorials work in Adonis 6, since you have so much stuff for A5 that I need to use.

If we were to modify this to Adonis 6, we would need to change that require to an import, right? I was thinking we would want to put "await import('./routegroup.ts')" where you have the require? I guess if the enclosing function is not already async we would have to use the .then construction. Hm. As you can see, I'm still trying to master these concepts

I noticed on some lessons, you have the text with screenshots like this one, and other lessons you don't. I love this format because I would much rather read than watch a video and it is great to be able to come back to it and scroll to the section I need. This is well-done. Hey, I put in a plug for Adonis to hire you for their tutorials when they start them :)

I love how you say Laravel is "kinda similar" to Adonis. That made me laugh. I came to Adonis from Laravel, and it feels like a port of Laravel to Node.JS. :)

this looks really cool. I had never heard of htmx. With htmx you can get an SPA feel with Edge templates.

Thanks Tom. I imagine you also will be updating a lot of your v5 lessons to v6. I really like your style. I find you way easier to understand than most tutorialists

It would be cool to get some tutorials on using other output options, like pushing to a SPA or using a different templating engine.