Expected current segment '' to be '$count', '$ref', or a bound operation

[kammaje_cis]

Hi @all,

I'm just playing with CAP Node.js flavour and Fiori Elements when found that if in my project folder I have something to render in the APP folder even the simplest GET requests goes wrong.

{
    "error": {
        "code": null,
        "message": "Expected current segment '' to be '$count', '$ref', or a bound operation"
    }
}

and if I delete that folder all HTTP requests goes ok.

For sure I'm doing something wrong in the APP folder while playing with FioriElements but the thing is that I could understand having some error while rendering the FioriElement's app BUT, why having this problem with just a GET request?

Does anybody know why? I got stucked digging at the schemas and DB's part when the problem is not there 🙂

[kammaje_cis]

app module usually has the application router. (file xs-app.json). That might be faulty.

[jsancho]

Thnx Marc, but in this case that is not the problem. Here is the thing:

1. If I have this "app" folder so that CAP will try to serve my INDEX.HTML file instead the "by default" entry page, if I execute a simple GET request (even w/o the last "/" 😉 ) it returns the already mentinoned error.

2. BUT if I just rename the "app" folder, so that CAP understand that there's nothing "special" to serve but the "by default" entry page, in that case the GET request goes ok.

That's the thing that I don't understand, why having this "app" folder makes CAP to behave different to the same GET request?

Later on I'll check if the content of my "app" folder is correct (for sure it's not), but I assume that replying to a given GET request has to behave always the same, no matter if the "by default" entry page or a custom one has to be served. Isn't it?