Open stefjoosten opened 1 day ago
This deployment is similar to what @hanjoosten , @Michiel-s and I did last week with project-template. The only difference is that I have customizations here. I excluded this by removing the customizations temporarily. The error messages were the same, so the customizations cannot explain this.
You probably cannot use your customizations as-is. We use angular now, not angularjs. Hopefully @Michiel-s can give you some hints/tips on how to upgrade.
The Ampersand code explains what happens here. Consider this snippet:
VIEW Kamer: RAV DEFAULT
{ "(" : TXT "("
, "id" : I
, ")" : TXT ") "
, naam : ravNaam
}
ENDVIEW
This translates to the following Typescript code in the front-end:
export type KamerView = {
(: '(';
I: string;
): ') ';
naam: string;
};
This is consistent with the TypeScript errors we got in this issue.
The obvious workaround is to avoid strings with special characters in the VIEW syntax.
From a user perspective, the error messages we get from npx do not point in the right direction. These messages are useless for Ampersand users. I can think of three different solutions:
I think it is a no-brainer that we should go for the second option. The label is given in interface.json
as a plain text without restrictions. I suppose that in handling this text at the frontend part it should be handled properly. So I expect this can be solved somewhere at the frontend code. @Michiel-s , do you agree?
What happened
I am generating an application on the new Angular front-end framework. Generation of the back-end fails with this message (a log fragment):
What I expected
Version of ampersand that was used
Steps to reproduce
1. 2. 3. 4.
Screenshot / Video
Context / Source of Dockerfile