monorepo

Expected Behavior

It should be possible to customize the header of the generated changelog (or omit it completely).

Current Behavior

The changelog header is hardcoded in https://github.com/lerna/lerna/blob/master/core/conventional-commits/lib/constants.js

Possible Solution

A `command.publish.changelogHea

When visual users look at a map they can easily tell that the controls, attribution, and other (potentially custom) UI components that are placed on the map belong to it. AT users rely on HTML semantics, DOM structure, and ARIA to convey these things and their relationships.

Currently, the tabindex="0", aria-label="Map" and role="region" (which to

When a contact is already added, open the contact profile or the existing conversation

The error check is done here: https://github.com/berty/berty/blob/097eb0229f22e2abce3addd750c8dce98e92845f/js/packages/components/modals/InvalidScan.tsx#L126

We shouldn't show the invalid scan modal but navigate instead

MGLTilePyramidOfflineRegion should have a countOfTiles method that returns the number of tiles included in the tile pyramid. The implementation would rely on the mbgl::util::tileCount() function added in #9906.

This is the iOS/macOS equivalent to #11108 for Android. It would serve as a built-in alternative to mapbox/turf-swift#47 for applications already using the map SDK, including applica

Real User-Agent is detectable with <iframe> when using "puppeteer-extra-plugin-stealth". To prevent it use "'--disable-features=site-per-process'" argument for puppeteer.launch(). See explanation: puppeteer/puppeteer#2548

Real screen size is also detectable with iframe, to prevent it I used preload() script.

OS: Windows 10
"puppeteer": 3.0.4
"puppeteer-extra": 3.1

Let's add MinVer and on successful builds generate a release.

Labeling subsystems with their backends would make it clearer which backends needed to be enabled in order to activate certain features. It would also make it safe(r) to render experimental backends on the docsite.

Relates to #8992.

Adding the new debugging capabilities (see title) within the devp2p packages along #1449 had the side effect of producing redundant messages on certain DEBUG logger combinations, mostly visible if the plain devp2p:* logger is used, see e.g.:

This is distracting and reduces ove

There is an issue when adding new languages that I believe is related to react suspense. See i18next/react-i18next#977

Error:

Steps to reproduce:

1. Add a new language to Locize.
2. Make su

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Component
The Dot browser uninstaller on Wind

I tried to create an iOS release build.

Steps to reproduce:

1. install pods
2. open Xcode Workspace
3. edit schema to release
4. start build

Looks like the bundler doesn't know the "ios" platform => no bundle creation.
"error Invalid platform "ios" selected"

+ node /Users/userName/RN-mono/node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev fals

In packages/components-typescript/package.json the fields main and main:src: refer to files that do not exist:

  "main": "src/index.tsx",
  "main:src": "src/index.tsx",

The index.tsx file is located in packages/components-typescript/index.tsx

Are these two fields redundant?