Open FlorianDue opened 1 year ago
I will try to fix those error messages. Could you provide the example file? It seems like these errors get larger if the PFDL file grows. I did not get such errors for small examples.
The naming restrictions allow us to distinguish between certain components (e.g. Task calls vs .Service calls). We would need additional keywords if we allow arbitrary naming of components. Currently, there is no plan to make such changes.
In the PFDL, only lowercase letters (e.g. fields in structures) or only uppercase letters (e.g. service names) are allowed as the first letter for some components. For users it is sometimes very difficult to understand the error, because the error message, depending on the content of the task can be quite large. The following error message is a result of writing ProductionTask instead of productionTask
In general, it would be very helpful for users to remove these restrictions on namings and allow all namings to start with either an uppercase or a lowercase letter.