Feature description

There should probably be dedicated features and tools for managing attachments.

Feature motivation

Dealing with attachments, and even finding them, can sometimes be challenging currently.

You can always make a suggestion as an issue tab for apps that are not on the list. I will personally check out the app and verify if it is working, properly mantained, safe to use (as a user not a security expert).
Translation is very much appreciated. You can either fork this and remake your own translation or use the same repo with me. I highly recommend translator to review the commit log e

Optionally it should be possible to explicitly end a connection after this one request by specifying this in tryEnd, end.

It would be nice to have code examples in the documentation for the props, as sometimes it can be hard to tell how to use a component and its props (especially for beginners)

I was thinking about implementing a custom controller for my setting but I'm not sure about which of the header files in firmware headers to include and/or inherit from as I can't find their related documentation nor comments inside the headers.

Looking at the con

What the hell means "it's very likely this issue is fixed."?
There should be a test and a proof the issue is fixed, this is not how issues works.

And, in fact, the issue CRYTEK/CRYENGINE#606 is not fixed and still present in 5.6

When there's a space in the engine installation folder, for example mine is in:

Describe the bug
Using application.NewWindow to create a secondary window, it's not possible to re-use that window after it has been closed. If the user presses the X button, the window doesn't respond to Show() calls any more.

To Reproduce

1. Create a main window
2. Create a secondary window
3. Close the secondary window
4. Attempt to re-show the secondary window.

Example co

I am relatively new to GitHub and even newer to Wiki.js & struggled for several hours to properly configure port 80 and 443 proxying to get the wiki my colleague built for our company to automatically work with port 80 & 443 and automatically redirect to port 443 and have it work properly with the wiki node proxy.

I would like to suggest a quick addition of a full proper nginx config (example b

It would be useful to have a model that associates text with text style properties, and can associatively combine into a sequence (a semigroup).

This doesn't need to be fancy to begin with, just the properties we have today (fontFamily, fontSize, color) would be useful, and we'd then have a nice base to extend with other properties.

Something like this:

module RichText : {
  t