Fix markdown formatting around ODataUriResolver

grstearns commented 4 years ago

Code block was closed incorrectly. Also removes an extra line of whitespace in the ODataUriResolver constructor block.

opbld32 commented 4 years ago

Docs Build status updates of commit b1f9a1d:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Details
_dependentPackages/CommonPlugins/tools/JoinTOC.ps1	:x:Error	Details
.openpublishing.publish.config.json	:x:Error	Details
[]()	:x:Error	Details

_dependentPackages/CommonPlugins/tools/JoinTOC.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/CommonPlugins/tools/JoinTOC.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1073741502
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/CommonPlugins/tools/JoinTOC.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset OData-conceptual. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset OData-conceptual step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

Line 138: [Error] W:\5lk4-s\.optemp\packages\opbuild.scripts.1.84.4\tools\opbuild\docset.prebuild.ps1 failed to execute

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

grstearns commented 4 years ago

Not quite sure what happened here. My best guess is that the old bad formatting crashed the script? Or maybe it's not related?

Either way, could I get a human to look at this?

mumbi-o commented 4 years ago

Hey @grstearns Seems the code formatting issue has since been fixed. I have removed the whitespaces you highlighted through 90e39f

MicrosoftDocs / OData-docs