headless

Currently, all Directus system collections have a description except directus_panels and directus_dashboards... let's add those:

Dashboards — Dashboards within the Insights module
Panels — Individual panels within Insights dashboards

https://leapgraph.com/graphql-api-security

This article mentions several add-on packages that Reaction may want to use. This issue is simply to investigate whether these vulnerabilities are present and try adding the packages to solve them.

Currently, catch block is the same for both methods in useForgotPasswordFactory (https://github.com/vuestorefront/vue-storefront/pull/5971/files/0e001721be751b0b0130915023ea0867722e1065#diff-89077440c1264480ee6ffbbcfb08d6c64c9881bea61ebbd8e0e5d260085b66ad):

err.message = err?.graphQLErrors?.[0]?.message || err.message;

Let's create an external function that takes care of that a

The default google-maps-input.json could maybe include more displaying options, such as themes and zoom level for the static map. Though hacky, these few changes do the job for me:

GeopointSelect.js

var _googleMapsInput = require('config:@sanity/google-maps-input');
var _googleMapsInput2 = _interopRequireDefault(_googleMapsInput);

class GeopointSelect extends _react2.default.Compone

when browsing, i should be able to perf-check right from the browser and results should be siphoned back to the extension.

Generate fixtures for models returned by our API. Instead of having one huuuge file with all of our fixtures, we would like to split these up, such that we have a dedicated file for each entity.

This ticket is for Admin Returns fixture

API Fixtures checklist → https://www.notion.so/medusajs/API-Fixtures-checklist-5abf366ac6784d4681344b97b3d4aedf

Loom on how to do API fixtures: https:/