Fredrik Karlsson
Fredrik Karlsson
We use populated entries in our frontend code and entry preview does not populate. So I added a "Populate" switch to collection preview settings and fetch linked entries in collection-entrypreview...
Moved select single collectionlink item selector to the left (to same place where the checkbox is when selecting multiple). Also made it into a primary styled button. 
We have added layout component previews for parent elements (ie. having children) and then it makes more sense to have the preview up on top with the heading instead of...
When adding a component, it is nice to see what parent it adheres to. Look at the following example:  Then it is nice to know what parent will receive...
When I try to create a new group, I receive the following error from the backend: ``` error: "invalid document for insert: keys cannot contain ".": "finder.path"" file: "/var/www/html/lib/vendor/mongodb/mongodb/src/Operation/InsertOne.php" line:...
This fixes some of features that I think are missing in Lokalize, which I love and use. Here are the features and my comments on why they are quality of...
When a translation value once has been set, it cannot be unset again. This PR removes values which are empty strings after trimming.
Show custom icon on LayoutComponents when it is set in options, like this: ``` { "icon": "/assets/app/media/icons/contacts.svg" } ``` There is no special icon picker or anything, but just a...
I get the following error when running Express v5: ``` TypeError: split(...).join is not a function at ...\node_modules\@wesleytodd\openapi\lib\generate-doc.js:73:47 at Array.forEach () at iterateStack (...\node_modules\@wesleytodd\openapi\lib\generate-doc.js:71:24) at ...\node_modules\@wesleytodd\openapi\lib\generate-doc.js:17:5 at Array.forEach () at...
When running with `@Execution(ExecutionMode.CONCURRENT)` on class level and `@Nested` test classes, it seems that all tests are named after the first nested test class that is run and then all...