headless

This is obsolete now that the collection navigation is configured through the data model settings page

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.

In an effort to improve our code quality we want to have make sure that all files in the repo pass linting.

Please see this guide for a step-by-step guide for how to complete this task: https://www.notion.so/medusajs/Lint-challenge-checklist-b4efc761cb36499abf4726cad0dd02e4

🚀