knochenmark / minesweeper Goto Github PK

The gridsize and amount of mines on the field should be based on the selected difficulty

Some difficulties to start with might be:

• Easy / Beginner
• Normal / Medium
• Hard / Expert

Store selected difficulty in localStorage for convenience

pass the values to the minesweeper component as props

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

• Easy 1 mine
• Medium 2 mines
• Hard 3 mines

Describe the bug
When starting a new game, sometimes (especially on hard) the first click will already trigger a bomb.
The fix of this would be a time-saver for power player.

To Reproduce

1. New Game
2. Click on random tile
3. Bomb explodes! If not, proceed with step 1

Expected behavior
In the "original" windows minesweeper the first click could never trigger a bomb. I guess the map was either generated on this first click, or several maps were generated and the first one without a bomb on the clicked tile was then used.

i.e.

1 = blue
2 = green
3 = red
4 = purple
5 = maroon
6 = turquoise
7 = black
8 = gray

0 no number should be displayed

We might want to consider adding a dark theme toggle button.
We have to cheack feasibility first.

• Should be able to select scores by difficulty
• just put it below the minesweeper component
• contains a list/table of highscores i.e. name, date, score
• can fill with mock data
• can contain a label like (coming soon)

Easy: 8 x 8 (64) fields and 10 Mines (16 %).
Medium: 16 x 16 (256) fields and 40 Mines (16 %).
Hard: 30 x 16 (480) fields and 99 Mines (21 %).

What do you think about that idea?

The timer can be used as highscore value on completion of the game.
Should be right aligned in the header. Styles should look like the mine counter. (done)

• Increase digits of mine counter and timer to 3

The devDependency @types/node was updated from 12.6.9 to 12.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

https://vincenttunru.com/migrate-create-react-app-typescript-to-create-react-app/

• Remove numbers on not-revealed mineFields

The devDependency @types/react was updated from 16.8.8 to 16.8.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Store in localStorage

When a flag is set on a tile and it afterwards left-clicked, the bomb explodes. The "original" windows-minesweeper had a securing mechanism to avoid left-clicks on flags. Flags had to be removed before the bomb can be triggered.

If this is by design, it is ok for me, but it just ruined a hard game for me just before winning.

Feature Request
The perimeter reveal, as described in #63, was programmed after the description in the wikipedia minesweeper article (I guess the german one, as I could not find notes in the english one). The wiki actually describes the behavior as MS minesweeper acts, whereas the functionality from #88 does behave differently:

• MS only reveals the surrounding non-flag fields, if the double-clicked field's number has as many flags in its perimeter, so only if e. g. a 2-field also has at least 2 flags in the 8 surrounding fields
• Knochenmark/minesweeper always reveals all surrounding non-flag fields

Solution
The perimeter reveal should only trigger, if sufficient flags are in the 8 surrounding fields, an additional check might be required.

Additional context
Try out here:
http://minesweeperonline.com/
Reveal a 1 field, right click and hold, and then also left-click to trigger the perimeter reveal, but it won't, as it has no flag. Then set a flag and try again.

preferably some svg icons, maybe try if theres something on https://iconmonstr.com

Triggered by double click auto reveals surrounding cells except flagged ones

Read something about this on the wiki page about minesweeper game. Never noticed there was such a functionality in place to be honest, but could be interesting to implement this. Maybe it plays smoother