-
Notifications
You must be signed in to change notification settings - Fork 16
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
Docs Porting Tool improvement #104
Labels
Comments
@jeffhandley @RussKie please feel free to edit the list with more tasks. |
This depends on the outcomes of the next week's meeting with @markwilkie. But if this tool is decided to be a part of Arcade, this will be the next priority because it will lay the foundation for other work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are several improvements we need to address to stabilize this tool for usage in all dotnet repos in an automated fashion.
P0
Before tackling anything else, we need to solve the following:
P1
Only tackle this after we fix the P0s:
<remarks>
item.<example>
item.-or-
lines in exceptions correctly, to ensure they have enough endlines so they render correctly in MS Docs.-or-
lines in exceptions with<br/>
or other features to ensure they get wrapped and save space.P2
Move the code from this tool into a forked arcade repo and adapt the two executables to be consumable by arcade.We already moved this tool to its own repo under dotnet.The text was updated successfully, but these errors were encountered: