gists | Utilities and samples that do n't warrant their own repo | Plugin library

The problem is in the line

arquivo_json = json.dumps(registro_json, indent=2, sort_keys=False)

Which according to the documentation, json.dumps "Serializes obj to a JSON formatted str according to conversion table"

In effect, the problem is that you are serializing the registro_json object twice, and ending up with a str. If you remove the offending line and directly pass registro_json to the gravar_arquivo_json function, everything should work.

Updated code:

It should return a list. After all, what you get from the releases endpoint, e.g. https://api.github.com/repos/python-babel/babel/releases, is a list.

Getting this right is surprisingly difficult, so I've tried to annotate the steps. There are a lot of annoying details.

At its core, this is just a manifestation of the dangling else ambiguity, whose resolution is pretty well-known (force the parser to always shift the else). The solution below resolves the ambiguity in the grammar itself, which is unambiguous.

The basic principle that I've used here is the one outlined several decades ago in Principles of Compiler Design by Alfred Aho and Jeffrey Ullman (the so-called "Dragon book", which I mention since its authors were recently granted the Turing award precisely for that and their other influential works). In particular, I use the terms "matched" and "unmatched" (rather than "open" and "closed", which are also popular) because that's the way I learned it.

It is also possible to solve this grammar problem using precedence declarations; indeed, that often turns out to be much simpler. But in this particular case, it's not easy to work with operator precedence because the relevant token (the else) can be preceded by an arbitrary number of newline tokens. I'm pretty sure you could still construct a precedence-based solution, but there are advantages to using an unambiguous grammar, including the ease of porting to a parser generator which doesn't use the same precedence algorithm, and the fact that it is possible to analyze mechanically.

The basic outline of the solution is to divide all statements into two categories:

• "matched" (or "closed") statements, which are complete in the sense that it is not possible to extend the statement with an else clause. (In other words, every if…then is matched by a corresponding else.) These
• "unmatched" (or "open") statements, which could have been extended with an else clause. (In other words, at least one if…then clause is not matched by an else.) Since the unmatched statement is a complete statement, it cannot be immediately followed by an else token; had an else token appeared, it would have served to extend the statement.

Once we manage to construct grammars for these two categories of statement, it's only necessary to figure out which uses of statement in the ambiguous grammar can be followed by else. In all of these contexts, the non-terminal statement must be replaced with the non-terminal matched-statement, because only matched statements can be followed by else without interacting with it. In other contexts, where else could not be the next token, either category of statement is valid.

So the essential grammar style is (taken from the Dragon book):

There is a mistake in getter selectedVideo:

It's solved. Apparently the error was not in the data class.

It was in the retrofit interface.

My interface WITH ERROR

You can work around this by rendering the Gist in an </code>:</p> <pre class="lang-html prettyprint-override"><code><!-- Gist.svelte --> <script> export let gistUrl = "" import { onMount } from 'svelte' let frame; onMount(() => { frame.srcdoc = `<script src='${gistUrl}.js'><${""}/script>`; }); </script> <style> iframe { border: 0; width: 100%; height: 100%; } </style> <iframe src="about:blank" bind:this={frame} title="Gist">

Try it in the REPL

You can use Sort dropdown for recently updated gists otherwise, there is no other feature like pin or star yet provided by github.

Problem solved I found something like:

I used the full git commit ID in the tag and my gists were displayed in the markdown file.

{% gist 1234567xxxxxxxxx.... %}

Weird when the 7 characters generally are enough. But this worked for me.