Skip to content

Conversation

@w1stler
Copy link
Member

@w1stler w1stler commented Dec 4, 2019

No description provided.

@w1stler w1stler changed the title [1] PR & issue template [1] PR & issue template fixes #1 Dec 4, 2019
@w1stler w1stler requested review from OtisRed and magul December 4, 2019 17:51
Copy link

@OtisRed OtisRed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just questions

#### Subject of the issue:
Describe your issue here

#### Your environment:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this, while working in docker?

Copy link
Member Author

@w1stler w1stler Dec 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By environment I meant production / RC / local. I am not sure if deployed envs' configuration will differ.

#### Migrations:
N/A

#### Rollback:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it too specific? As I understand rollback means reversed migration (does it?), in which case we would hardly ever use that field and even if we do, "Migrations" still seems to be the likely place I would mention it

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Defaultly it would be N/A (or the previous version mentioned), but I would stick with that as a good practice. Nevertheless could be removed. ;-)


#### Your environment:
* version/branch
* which browser and its version
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that there's much of use out of it, we can probably assume that every member is using a "recent enough" one.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto, I would leave it as a good practice.

N/A

#### Unit Tests:
N/A
Copy link
Member

@arturtamborski arturtamborski Dec 5, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does it mean? Should I list unit tests here? Or describe what I (potentially) added to the testing suite?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When you don't have a habit of writing tests this could be actually self-reflective. "Oh so... I wrote this function so what kind of tests do I need here? Since it is expected to list sth...".

Also this could be early checker for complexity od the code. If you have a lot of those the chance is that you like spaghetti, aren't you? :D

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hard-copy from other project. :D Could be removed.

N/A

#### What tests do I need to run to validate this change:
N/A
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 💯

@arturtamborski
Copy link
Member

Resolves #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants