Skip to content

Conversation

v-alje
Copy link
Contributor

@v-alje v-alje commented Jun 27, 2018

This is a bulk fix to remove spaces from between the square brackets "]" and the parentheses "(" of markdown links. This fixes a content issue that the Localization team is seeing where loc content is broken compared to English. User Story 1292440
Related to #6169

@@ -131,7 +131,7 @@ from (C as c join D as d) cross apply c.Names as e
from (C as c join D as d) cross apply c.Names as e
```

In [!INCLUDE[esql](../../../../../../includes/esql-md.md)] (unlike [!INCLUDE[tsql](../../../../../../includes/tsql-md.md)]), the `FROM` clause only introduces the aliases into scope. Any references to columns (properties) of these collections must be qualified with the alias.
In [!INCLUDE[esql](../../../../../../includes/esql-md.md)](unlike [!INCLUDE[tsql](../../../../../../includes/tsql-md.md)]), the `FROM` clause only introduces the aliases into scope. Any references to columns (properties) of these collections must be qualified with the alias.
Copy link
Contributor

@pkulikov pkulikov Jun 27, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm afraid the most of the changes in this PR remove correct white spaces.

For example, this paragraph is responsible for the following section:
https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ef/language-reference/from-entity-sql#semantics

In Entity SQL (unlike Transact-SQL), the FROM clause...

Note that white space is correct.

In general, all structures of the form

[!INCLUDE[<name>](<link>)]

require white space after it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @pkulikov, @v-alje. This can't be a bulk change operation. Along with removal of valid whitespace characters, these changes introduced six build breaks. My sense is that the best approach is to close this PR and submit a new PR that doesn't do a bulk change in eliminating whitespace characters.

[Previous] (index.md)
[Next] (../Microsoft-platform-tools-containerized-apps/index.md)
[Previous](index.md)
[Next](../Microsoft-platform-tools-containerized-apps/index.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@v-alje that looks that real issues to fix are in the following folder:
https://github.com/dotnet/docs/tree/master/docs/standard/containerized-lifecycle-architecture

My recommendation to you is to create a new PR that updates the files only from that folder: that one would be much easier to review and most probably it would be the one catching the majority of such mistakes in the docs.

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see @pkulikov and @rpetrusha earlier comments. Based on the earlier PRs I saw, the links breaking LOC were the Previous and Next buttons. Can we focus this PR on only those files?

@v-alje
Copy link
Contributor Author

v-alje commented Jun 28, 2018

@mairaw @pkulikov @rpetrusha
Closing this pull request and will push up a new fix for the spaces shortly.

@v-alje v-alje closed this Jun 28, 2018
@v-alje v-alje deleted the space-link-bulk-fix branch June 28, 2018 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants