I'd like to contribute this example. It does not work on mobile which would require DOM Touch support but I think it's still very useful.

https://svelte.dev/repl/e5d53d675f444311a908121494f51aa6?version=3.15.0

Search does not work on the documentation site. The console shows an AlgoliaSearchError with the message: "Invalid Application-ID or API key".

Steps to replicate

1. Go to the docs.
2. Open your browser's devtools and open console.
3. Type a query into search bar (ex: "model").
4. After a few seconds, the errors show in console.

Error object

``

Howdy tb folks,

Ran into an issue where I was trying to debug an application for someone that was experiencing this error message. Unfortunately it's quite a vague error message and doesn't really explain why having this value is set. It might be useful to explain why this is bad, or link to some documentation.

If you have a preference on either making the error message longer to provider mo

Hi,

Description

I asked myself how to easily add a "post article" custom content (right just before closing </article> (or after ?) BUT inside the <main> tag ?

Goal

My goal is to add static content on very page above the main content, at template level using native override capabilities.

Detai

In FF (57+) the selected item toggles between the correct one, bar, and the first one foo.

With Chrome (62.x), it works as expected: bar is always selected (and displayed).

I read again the documentation about boolean attrs. :)
Am I missing anything here?

class Foo {
    static init() {
        const render = hyperHTML.bind(document.querySelector("foo"));

     

Your Travis build configuration is outdated; Python 3.2 should be removed.
While building PyYAML wheel: #error Cython requires Python 2.6+ or Python 3.3+.

It took me ages to work out how to get JSON to work on the command line. A quick example in the documentation would be useful. Example:

markdown-pdf --remarkable-options '{"preset":"full"}' myfile.md

Question

Relating to this issue graphql-dotnet/authorization#11.
Currently, the template reference GraphQL.Authorization and replicate the work done in this pull request
graphql-dotnet/server#171

Should the template use the ASPNetCore version instead for the same reason that you discussed in graphql-dotnet/authorization/issues/11 ?

• I'm submitting a ...
  [x] feature request

• Summary

tslint has a language service plugin so that tslint runs within the language service and shows linter failures in your editor as red squiggly underlines, the same as type errors.

https://www.npmjs.com/package/tslint-language-service

I'll make a PR at some point; just logging here for the time being.

Maybe the API has existed for too long to change this now, but I found it confusing that the encodeURI helper calls encodeURIComponent, the naming of the helper maps very neatly to the javascript functions that are so familiar to us, but the functionality differs.

Would it not more accurately reflect its function if the helper were renamed to encodeURIComponent?

To Reproduce

Clone this repo.
Run yarn.
Run yarn test.

Expected behavior

The test should pass with no warning. Although the test passes, doing other tests with the EmailEditor component will fail for the same reason as the warning given:

React.createElement: type is invalid -- expected a string (for built-in components) or

In mobile, I see the header menu expanded vertically.

This doesn't look good to me. I think it'd be better a collapsible menu.

• Improve documentation on how to author templates.
• Add documentation on the packaging and distributing of WinTS compatible templates. This must also include differences from how dotnet-new works with template sources.
• Improve tools to help with testing and validating any created templates. Existing tests and tools are a start but these may need updating and revising to make them

Spring v3 functions look great! However it looks like current (non v3) versions of Helm are pinned to Sprig v2. Some kind of note that the documentation is for v3 and not v2 would be useful. Having v2 documentation also available online would be nice, too. And I would also recommend a practice of having "introduced in version" notes on new functions going forward, or perhaps an outlink to a Ch

As PWA add to home screen workflow is different on each platform/browsers, we could add a button on the interface to trigger the installation. It will standardize add to home screen workflow for all browsers.

See official doc
for more informations