Skip to content
#

development

Here are 2,386 public repositories matching this topic...

njacharya
njacharya commented Aug 16, 2019

A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

feross
feross commented Aug 18, 2019

https://eslint.org/docs/rules/func-call-spacing

When calling a function, developers may insert optional whitespace between the function’s name and the parentheses that invoke it.

Option: "never" (default) disallows space between the function name and the opening parenthesis.

Examples of incorrect code for this rule with the default "never" option:

/*eslint func-call-spacin
iamnewton
iamnewton commented Feb 21, 2017

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

  • who? - who wrote the p
rondonjon
rondonjon commented Feb 26, 2020

The react/display-name documentation doesn't explicitly state it, but the rule seems to accept display names as properties inside components.

=> Documentation needs to be updated

When the displayName was defined as a property, I think the rule should ensure that the declaration is static, so the following case should be rejected:

class Demo extends Component {
  displayName 
guyho
guyho commented Dec 27, 2019

There is no warning about the number of computing resources that a default configuration will take.

Expected Behavior

Indication on the expected computing resources required. Ideally checking the available resources and warning when not enough are available, implying some applications may need to be closed before running a default configuration/workspace.

Current Behavior

The configu

Sispheor
Sispheor commented Aug 1, 2018

General information

  • Minishift version:
minishift version
minishift v1.22.0+7163416
  • OS: Linux
  • Hypervisor: KVM (in nested VM in VMware)

Steps to reproduce

[root@TSKERCBOFRAP01 ~]# printenv |grep NO_PROXY
NO_PROXY=localhost

minishift start
-- Starting profile 'minishift'
-- Using proxy for the setup
-- Check if deprecated options are used ...
djfarrelly
djfarrelly commented Mar 19, 2019

Purpose

I think it would better for Docker container security to not run the main command on a port under 1000.

Idea

Change the Dockerfile to run on 1080 / 1025 instead of 80 / 25. The challenge is that this could break people's usage when upgrading so we'd have to think about this one or save it for a 2.x breaking changes release.

Improve this page

Add a description, image, and links to the development topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the development topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.