| Summary: | Parser should warn when there is anything on the Protected Area beginning line | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Laurent Goubet <laurent.goubet> | ||||
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | stephane.begaudeau | ||||
| Version: | 3.0.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 185522 [details]
Patch
Contributed on HEAD available in Acceleo 3.1 M5.
Fixed |
Protected areas in Acceleo are identified through an unique ID. This ID is what is passed as parameter of the protected block : [protected ('myID')] [/protected] This ID can contains whitespaces : we consider the "end of ID" to be the following carriage return. As such, protected areas such as : <!--[protected ('myID')]--> <!--[/protected]--> or [protected ('myID')][/protected] won't work as expected (in the generated code, these would look like : <!--Start of user code myID--> <!--End of user code--> and Start of user code myIDEnd of user code which mean that "something" is appended at the end of the ID, and Acceleo won't be able to match this ID when next generating.