-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate new lines in template files #1157
Comments
The files in the repo are properly setup, it looks line May be related to dotnet/templating#1248 |
The wizard is using |
Researched on stack overflow to this issue And checked the unoapp folder in the templates repo here And on the file ending .xaml there is none of this line ending attributes like on the xml or cs ones. On my fresh creates projects this issue is only and every time happening on xaml files, in the area of the namespaces and somewhere below but did not paied closer attention to this. Also wondering about why there are different settings (lf and sometimes crlf) applied? Is there a reason why you choosen this instead of maybe lf for all? Windows prefers crlf and I do use it also in vs2022 but I think you might have had a reason to decide to this setting isnt it? |
From #741 - The EOL around these lines:
appear to be
(and similar lines) |
@MartinZikmund I would like to try out to pass a linebreak maybe in the xaml file which are having this issue, as alternative solution for this this on a forked branch, but dont know how I could set up that correctly, could you maybe help me with this? How could I change that files in a local project and let it create a new one from that templates instead? I compared the templates here in the repo and the lines, the CR LF Dialog is changing.
So what I am seeing is:
|
What would you like to be added:
unoplatform/uno#18989
Based on this report, new lines might not be consistent across all template-generated files
Why is this needed:
For which Platform:
Anything else we need to know?
The text was updated successfully, but these errors were encountered: