Fanatic | 饭否 Chrome 扩展 : 按照关键字、通配符、正则表达式筛选饭否时间线消息 , 并过滤或染色 | Browser Plugin library

The problem is that your read_json(....).text line returns a series, not a dataframe.

Adding a .to_frame() and referencing the column in the following line should fix it:

Can you try wrapping content inside App.js with BrowserRouter as below

You're referencing javascript with the wrong tag.

Javascript should be referenced with a

It worked here and in codepen site, because both are not using a reference to the javascript, they are "creating one".

EDIT: To avoid the following error in the repl.it site:

The type you are getting with findViewById is potentially unconstrained so the type cannot be inferred and in Kotlin needs to be explicitly stated/casted.

If you are targeting API 26 or higher in your app you can do:

If you want to update a dataframe with more than 1M rows, than you definetely want to avoid for loops whenever possible. There is an easier to update your 'Category' column, like it was done here.

In your case, you just need to convert your 4 lists with the badges names to a dictionary matching the badge name to its numerical category, like:

I don't know what would happen there on a technical level, but it doesn't look good. I would recommend not doing that. It's far easier and less error-prone IMO to initialize high level systems like networking and whatnot inside a separate Init() method in your class. That way you can safely create an instance, call its Init() method, check the result, and delete (or call a Destroy(), or both) on failure.

I would only assign default values inside the constructor and let outside code call your destructors with delete.

There is an important distinction that is required for this question. Note that this is valid for almost any GUI based environment/framework, not just Qt.

I will cite the description in the related Wikipedia article:

A mnemonic is an underlined alphanumeric character, typically appearing in a menu title, menu item, or the text of a button or component of the user interface. A mnemonic indicates to the user which key to press (in conjunction with the Alt key) to activate a command or navigate to a component.

Depending on the platform and framework in use, but most importantly the source of the mnemonic, the behavior can slightly change.

For buttons or "buddies" (labels that are linked to another widget in order to use their mnemonic to set the focus on that widget), the mnemonic usually works with Alt+letter.
For menu items, instead, it's usually enough to directly press the letter without the Alt modifier.

They are (usually) keyboard combinations, using at least one or more modifiers and another standard (possibly) alphanumeric key.
A typical example is Ctrl+A, used to select everything in the current object.

Note that while conceptually a mnemonic _is_ a keyboard shortcut, and technically you can construct a keyboard shortcut without any modifier, it's common convention to differentiate them (and avoid shortcuts without modifers).

In Qt mnemonics exist in the following cases:

• actions (when they're added to a QMenu or a QToolbar)
• buttons (QAbstractButton subclasses)
• tabs (QTabBar tabs, usually for QTabWidget)
• group boxes (QGroupBox)
• labels (using setBuddy()

In all situations they are shown with the mnemonic letter underlined^[1], and that letter can be explicitly set using the & character preceding the letter that is going to be used (the ampersand can be actually shown using &&), otherwise the style will autonomously try to set them.

An important note about the last case (letting Qt set the mnemonics). The style set for the application (the default one or that set using setStyle()) or for a specific widget not only sets mnemonics on its own^[2], but it will also overwrite the object text() property. If you create a button with its text as "Button", not only Qt will probably use the "b" letter for its mnemonic, but button.text() will also return "&Button". Note that this does not happen within the creation, but only as soon as the widget is added to a parent and that parent is shown.
That is another very important reason for which object comparison (if someWidget.text() == 'someText': do something) should never be done using the text() property.

An other important aspect to consider about mnemonics is that only the first &-preceded letter will be used for the mnemonic. If you create a button with text "&Some &button", only the "S" letter will be considered (even if the "b" will still be probably underlined). Not only: if you try to use the same multiple &-based mnemonics on different widgets, the result will be undefined^[3].

Now. Qt Designer doesn't allow to create shortcuts for specific widgets arbitrarily, and that's for good reasons: keyboard shortcuts should be unique and need context. UIs created with Designer should be as much universal as possible and should not go too "deep" in implementations that should be done on the logic side of the programming. QActions are designed for that, to be "actions" possibly executed out of any context, unlike standard widgets which depend on keyboard focus and mouse position, and that's why you can set shortcuts for them.

Finally.
If you are just looking for mnemonics, follow the above suggestions about them.
If you need something that could actually be activated from anywhere, create a QAction, and connect its triggered signal to the related function within the code; if that something is going to appear on menus or toolbars also, you can create the related QAction on Designer.

_Notes:
¹ Some styles (notably, "breeze") only shows underlined letters when the Alt is pressed.
² Automatic mnemonics are created in insertion order to their parent, recursively.
³ Try creating two buttons with the text "&test &button": the second button will probably appear as "test &button".

In your case, I would recommend treating warnings as error so that your gated commit will fail if the project contains warnings - here an example for dotnet core:

The error is telling you that instagramData.user is undefined. Most likely this happens the first time the component is rendered before the request to instagram comes back with a response. You need to handle this situation gracefully by either not displaying the user data at all until the response comes back or displaying some kind of static place holder. One way to do this is with conditional rendering: