interface | 基于koamongodb为前端提供接口

You can set up a signal handler for the SIGWINCH signal, and you will get this signal whenever the terminal size changes. Note that, as with all signal handlers, any code in the signal handler must be signal-safe.

If you are using the curses library, you will get a KEY_RESIZE key, and then check COLS and LINES.

The problem is that you are using an empty notesListAll list for filtering results; you need to populate it with the list of notes in the constructor

Try using a state operator to update the state. For example, you could use the updateItem to find and update an item in an array:

Nuxt makes the $config available in two ways: as this.$config on every component instance, and context.$config passed to "special nuxt lifecycle areas like asyncData, fetch, plugins, middleware and nuxtServerInit" (docs).

It looks like you need to access the $config outside a component, so you'll need to retrieve it early in the request cycle. In particular, since you're mutating the Vue.prototype, this feels like a good fit for a plugin in the Nuxt sense, which isn't quite what you've got in your code.

If you put your plugin file in the plugins directory and reference it from the plugins array in nuxt.config.js (see link above for a broader example), you could rewrite it like this to access $config:

From what it looks like, options is actually an array of objects rather than just an object. So all you would need to do is map over the options variable. You are currently using Object.keys which is what you use if you are wanting to iterate over the keys in an object.

I think fundamentally the problem is that it gets stuck going down the wrong path. It sees a field of length 2, which we know is the minutes but it believes is the hours. Once it believes the optional section is present, when we know it's not, the whole thing is destined to fail.

This is provable by changing the minimum hour length to 3.

See microsoft/TypeScript#43667 for a canonical answer. This is a design limitation of TypeScript.

As you might be aware: in TypeScript's structural type system, Child is a subtype of Base even though it is not explicitly declared as such. So every value of type Child is also a value of type Base (although not vice-versa). That means Child | Base is equivalent to Base... although the compiler is not always aggressive about reducing the former to the latter. (Compare this to the behavior with something like "foo" | string, which is always immediately reduced to string by the compiler.)

Subtype reduction is often desirable, but there are some places where Child | Base's behavior is observably different from Base's, such as excess property checks, IntelliSense hinting, or the sort of unsound type guarding that happens with the in operator. You haven't shown why it matters to you that you are getting a Base as opposed to a Child | Base, but presumably it's one of these observable differences or something like it.

My advice here is first to think carefully about whether or not you really need this distinction. If so, then you might consider preventing Base from being a subtype of Child, possibly by adding an optional property to it:

You can use a type predicate to define a user-defined type guard like this:

You are missing the listener type configuration so the default conversion service sees you want a list and splits the string by commas.