-
-
Notifications
You must be signed in to change notification settings - Fork 248
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
Syntax Lookup: ignore() function #570
Syntax Lookup: ignore() function #570
Conversation
@@ -409,33 +409,36 @@ add(1, 2); | |||
|
|||
</CodeTab> | |||
|
|||
If you need to call a curried function with a single unit `()` argument, you can use the `ignore()` function: |
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.
🗒️ Looks like this is no longer required for v10?
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.
Indeed, plus it should have said "uncurried".
| Decorators | ||
| Operators | ||
| LanguageConstructs | ||
| BuiltInFunctions |
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.
🗒️ New category
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 looks great, thanks for that.
Just a question: should this also show up in the overall search?
In other words, it's generally not clear to me when one should reach for the overall search (the one powered by algolia), and when one should reach out for syntax lookup.
It's a good question. It was originally inspired by a JS syntax lookup. Here's how I think about it at the moment: [1] Syntax Lookup on its own provides a quick reference / cheat sheet of syntax. Since the Syntax Lookup only contains summarised information that is already on the primary documentation pages, perhaps it's not necessary to include in Algolia? @ryyppy what do you think? |
LGTM. Regarding Algolia: I think the widget pages should not show up in the search results for the same reasons you just mentioned. |
Hi team, suggestion for #162 and #448