Skip to content
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

markdown file which generate on windows machines have other eol #112

Closed
danielleroux opened this issue Nov 3, 2022 · 2 comments · Fixed by #148
Closed

markdown file which generate on windows machines have other eol #112

danielleroux opened this issue Nov 3, 2022 · 2 comments · Fixed by #148
Assignees
Labels
type: bug Something isn't working

Comments

@danielleroux
Copy link
Collaborator

I'm submitting a...


[x] Bug report
[ ] Feature request
[ ] Documentation issue or request

Current behavior

If you execute the library build task. The new generated markdownfiles for documentation contains different line endings for example macOs and windows

@danielleroux danielleroux added the type: bug Something isn't working label Nov 3, 2022
@danielleroux
Copy link
Collaborator Author

danielleroux commented Nov 16, 2022

Autogenerated documentation code is not part of the version control anymore #117

@PhentomPT
Copy link
Contributor

@danielleroux since the auto-generated files were removed i think it does not happen anymore.
The only files that is generated differently now is the component-doc.json from core that i have a MR to fix the eol characters #148

@danielleroux danielleroux linked a pull request Nov 17, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants