Everything in routes.swift?

[jaysonng]

Hi,

Currently all cloudcode needs to be in routes.swift?

There's no way to separate code into their own files for maintainability?

thanks,
Jayson

[cbaker6]

This question is related to how to use Vapor as oppose to ParseServerSwift. Here’s a couple articles that shows how to register Vapor routes created in different files.

• https://alexandrecools.medium.com/vapor-routes-groups-and-collections-5ff920720317
• https://medium.com/@cweinberger/routing-in-vapor-4-b49ad909e33c

[jaysonng]

There may be a bug with routing and collections.

    func boot(routes: RoutesBuilder) throws {
        
        let lokalityGroup = routes.grouped("lokality")
        lokalityGroup.post("first", name:"first", use: getLokalityFirst)
    }

With this code, I get a webhook that has a destination address /first instead of the expected http://127.0.0.1/lokality/first

Bug right?

[cbaker6]

This doesn't look like a bug to me, ParseServerSwift doesn't know how to read "grouped" and doesn't extend HTTPRoutesGroup, it extends RoutesBuilder instead. You will have to define the path manually like I showed #38 (reply in thread).

It's possible that using grouped is a feature request that can help build paths, if so, you would need to open an issue and ask for the feature. Then you can attempt to open a PR to add the feature and I can review.

[cbaker6]

Without a PR, you can probably get away with some variation of:

func boot(routes: RoutesBuilder) throws {
        
        let lokalityGroup = routes.grouped("lokality")
        let path = lokalityGroup.append("first")
        lokalityGroup.post(path, name:"first", use: getLokalityFirst)
 }

[jaysonng]

It's possible that using grouped is a feature request that can help build paths, if so, you would need to open an issue and ask for the feature. Then you can attempt to open a PR to add the feature and I can review.

Right. Sorry. I should have said feature request.

Ill do a Feature request but ill also try the append trick.

Thank you,

[cbaker6]

@jaysonng it turns out you were correct and this is actually a bug in ParseServerSwift, will be fixed in #41