-
Notifications
You must be signed in to change notification settings - Fork 105
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
uid: microsoft.quantum.lang-ref.entrypoint | ||
--- | ||
|
||
# `@EntryPoint` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This and @Test
are both attributes that are already documented in the API reference; can we link to those from the TOC rather than duplicating that content?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cgranade That's a great point, thanks. Just to clarify, it sounds like you mean keeping the links in the TOC dropdown (and the keyword list page), but simply linking direct to the API page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that should work, yeah. If I recall, you can make href
properties in toc.yml
point to xrefs instead of Markdown file paths; that would allow for reusing the automatically generated references for Test and EntryPoint.
Docs Build status updates of commit a516dd2: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
articles/user-guide/language-ref/toc.yml
For more details, please refer to the build report. If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
Docs Build status updates of commit 4a0e1bf: ✅ Validation status: passed
This comment lists only the first 50 files in the pull request. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
@gillenhaalb is this PR outdated/closeable? |
@geduardo Its motivation is definitely still there and it will be my priority after Learn, but I would file it under "perhaps" closeable. The reason being that there wasn't too much work done on the pages themselves, but the skeleton that's setup currently is still essentially what we'll use. The only outdated part is the links to the language ref pages will be updated to xrefs now that we're hosting them in the same docset. Since setting up the skeleton was somewhat laborious, we wouldn't want to have to re-do all of it. However, there is still a hefty amount to be done on the pages (descriptions, code examples, etc.; which will probably get a few others involved) and it shouldn't stand in the way of migration, so I'd say it would certainly be closeable provided we don't delete the branch. Should I go ahead and close? |
On hold until migration to Q# language repo is settled (links will all direct to respective pages there).
Addresses the broader discussion in #939. Creates separate pages for each Q# keyword (for searchability). Also some language constructs/symbols.
Content for pages:
To-do:
Additional pages to be added:
!
unwrap operator< >
type parameterized callablesw/ <-
copy-and-update expressions (array elts and named itemsw/= <-
update-and-reassign statements (used withset
for named items and array items)? |
conditional expression