Supercup stats & predictions

*/} {/*n*/} {/*tn*/} tn {/* tn */} ); } } function mapStateToProps(state){ return{ hasStarted : state.timerReducer.hasStarted, currentMeditationType : state.timerReducer.currentMeditationType, secondsLong : state.timerReducer.timeLength * state.timerReducer.timeLengthMultiplier, secondsShort : state.timerReducer.shortBreak * state.timerReducer.shortBreakMultiplier, secondsMedium : state.timerReducer.mediumBreak * state.timerReducer.mediumBreakMultiplier, secondsLong : state.timerReducer.longBreak * state.timerReducer.longBreakMultiplier, secondsRest : state.timerReducer.rest * state.timerReducer.restMultiplier, secondsCountdown : state.timerReducer.countdown*state.timerReducer.countdownMultiplier, minutesCountdown : Math.floor(state.timerReducer.countdown*state.timerReducer.countdownMultiplier /60), timeLength : state.settings.timeLength, shortBreak : state.settings.shortBreak, mediumBreak :state.settings.mediumBreak, longBreak :state.settings.longBreak, rest :state.settings.rest, countdown :state.settings.countdown, timeLengthMultiplier :state.multiplier.timeLengthMultiplier, shortBreakMultiplier :state.multiplier.shortBreakMultiplier, mediumBreakMultiplier :state.multiplier.mediumBreakMultiplier, longBreakMultiplier :state.multiplier.longBreakMultiplier, restMultiplier :state.multiplier.restMultiplier, countdownMultiplier:state.multiplier.countdownMultiplier, } function mapDispatchToProps(dispatch){ return bindActionCreators({ setSecondsLeft }, dispatch); } export default connect(mapStateToProps,mapDispatchToProps)(Timer);<|file_sep|>.settings__container{ margin-top:5rem; text-align:center; width:max-content; max-width:max-content; min-width:max-content; padding:.5rem .25rem; background-color:#fff; border-radius:.25rem; display:flex; flex-direction:column; align-items:center; box-shadow: inset -5px -5px .25rem rgba(0,0,0,.05), inset -5px -5px .25rem rgba(0,0,0,.05), inset -5px -5px .25rem rgba(0,0,0,.05), inset -5px -5px .25rem rgba(0,0,0,.05), inset -5px -5px .25rem rgba(0,0,0,.05), inset -5px -5px .25rem rgba(0,0,0,.05); animation-name:morphSettingsContainer; animation-duration:.75s; animation-timing-function:cubic-bezier(.4,.02,.27,.86); animation-delay:.75s; animation-fill-mode:both; animation-iteration-count:infinite; } @keyframes morphSettingsContainer{ from{ transform: scale(.7) skewX(-30deg) skewY(-30deg) scaleX(.7) scaleY(.7) skewX(-15deg) skewY(-15deg) scaleX(.9) scaleY(.9) skewX(-10deg) skewY(-10deg) scaleX(.95) scaleY(.95) skewX(-6deg) skewY(-6deg) scaleX(.98) scaleY(.98) skewX(-4deg) skewY(-4deg) scaleX(1) scaleY(1); scaleX(.99) scaleY(.99); scaleX(.995); scaleY(.995); transform-origin:right bottom; scaleZ(.01); rotateZ(180deg); scaleZ(10000); rotateZ(-180deg); transform-origin:left bottom; transform-origin:left center; rotateZ(180deg); scaleZ(.01); rotateZ(-180deg); scaleZ(10000); transform-origin:right center; transform-origin:right top; rotateZ(-90deg); scaleZ(.01); rotateZ(+90deg); scaleZ(10000); transform-origin:left top; transform-origin:center bottom; rotateZ(+90deg); scaleZ(.01); rotateZ(-90deg); scaleZ(10000); transform-origin:center top; } to{ transform: scaleX(1.) scaleY(1.) transform-origin:center center; transform: scaleX(1.) scaleY(1.) transform-origin:right bottom; scaleZ(.01); rotateZ(+90deg); scaleZ(10000); transform-origin:left bottom; transform-origin:left center; rotateZ(+90deg); scaleZ(.01); rotateZ(-90deg); scaleZ(10000); transform-origin:right center; transform-origin:right top; scaleZ(.01); rotateZ(+90deg); scaleZ(10000); transform-origin:left top; transform-origin:center bottom; rotateX(+90deg); scalez(.01); rotateX(-90degs); scalez(zero); } }<|repo_name|>jimmygolovanov/meditation-app<|file_sep||**O**bserve **A**lways **W**ith **S**erenity| ============================================= ### A meditation app built using ReactJS.  This project was bootstrapped with [Create React App](https://github.com/facebookincubator/create-react-app). ## Installation Instructions: Clone repository: git clone https://github.com/jimmygolovanov/meditation-app.git Install dependencies: npm install Run application: npm start ## Project Details: This project uses [Redux](https://redux.js.org/) as its main data management tool. The project uses custom animations created using CSS animations. The user interface is responsive. <|repo_name|>jimmygolovanov/math-game<|file_sep[build-system] command="yarn build" publish="build" [build.environment] NODE_VERSION="12" NPM_VERSION="6" YARN_VERSION="v1" # YARN_FLAGS="--ignore-engines" # Uncomment line below to ignore engines check when installing dependencies. # YARN_FLAGS="--frozen-lockfile" # Uncomment line below to use frozen lock file when installing dependencies.<|file_sep�How do I play? You have two options here: Click "New Game" button at top left corner. Or click "New Game" button inside game board. Then choose your difficulty level. After choosing difficulty level you will be redirected back into game board. In game board you will see three buttons at right side. First one is New Game button which you already know what it does. Second one shows your score. Third one shows your highscore which gets updated every time you play. Each box has two numbers in it. First number represents how many times you have played that particular box before. Second number represents how many times you have answered correctly that particular box before. You need to find sum of numbers inside boxes which are adjacent to each other horizontally or vertically. For example look at image below:  Sum of all numbers inside boxes which are adjacent to each other horizontally or vertically is:  So answer would be `16`. You need enter your answer into input field provided at bottom right corner. If answer is correct then score gets incremented by `one`. And answer field gets cleared so you can enter another answer. ### How does scoring work? Each correct answer gives `one point`. But more important thing here is that how many times you have played that particular box before. For example look at image below:  As per above image we can see that box `(row=4,col=4)` has been played `four times`. And out of those four times we got correct answer `two times`. Now let's say we get correct answer again then score gets incremented by following formula: score+=baseScore*(totalNumberOfTimesPlayedThatBoxBefore)/(totalNumberOfTimesAnswerWasCorrectThatBoxBefore) // For above example baseScore=one so score+=one*(four)/(two)=two points ## Installation Instructions: Clone repository: git clone https://github.com/jimmygolovanov/math-game.git Install dependencies: npm install Run application: npm start ## Project Details: This project uses [Redux](https://redux.js.org/) as its main data management tool. The user interface is responsive. To learn more about create-react-app check out [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started). To learn more about redux check out [Redux documentation](http://redux.js.org/). To learn more about react-redux check out [React Redux documentation](https://react-redux.js.org/introduction). This project was bootstrapped with [Create React App](https://github.com/facebookincubator/create-react-app). You can find most recent version on npm under [@babel/cli](http://www.npmjs.com/package/@babel/cli). ### Available Scripts In order to run locally copy `.env.example` file into `.env` file located at root directory. In order to run locally copy `.env.example` file into `.env.local` file located at root directory. In order run locally copy `config.example.json` file into `config.json` file located at `/server/config` directory. #### `npm start` Runs the app in development mode.
Open [http://localhost:3000](http://localhost:3000) to view it in browser. The page will reload if you make edits.
You will also see any lint errors in console. #### `npm test` Launches the test runner in interactive watch mode.
See section about [running tests](#running-tests) for more information. #### `npm run build` Builds production bundle(s). See section about [deployment](#deployment) for more information. #### `npm run eject` **Note:** this is a one-way operation. Once you `eject`, you can’t go back! If you aren’t satisfied with Create React App’s build toolchain and configuration choices,
you can “eject” to customize it. This command will remove all traces of Create React App
and leave you solely with the build tools and configuration files it depends on.
You’ll be on your own from here! When you eject, all configuration files and transitive dependencies
(babel-loader etc.) will be copied into your repository so you have full control over them.
At this point you’re on your own.
You don’t have to ever use `eject`. The curated feature set is suitable for small
and middle deployments, and you shouldn’t feel obligated to use this feature.
### Deployment See section about [`npm run build`](#npm-run-build) command for more information. ### Learn More You can learn more in Create React App’s documentation:
- [Getting Started Guide](https://facebook.github.io/create-react-app/docs/getting-started)
- [User Guide API Reference](https://facebook.github.io/create-react-app/docs/api-reference)
To learn React check out [the React documentation](https://reactjs.org/). #### Advanced Configuration ##### Environment Variables >Note: You must create a `.env.local` file alongside your `.env.example`. There are times during development when you might want to use different environment variables depending on your local environment e.g., using different ports etc... To achieve such functionality create-react-app supports loading environment variables from .env.local files automatically without any need to restart server unlike normal node applications where node process needs restarting whenever there are changes made within .env files. An example usage would be setting different port number based upon whether environment variable NODE_ENV equals production or development e.g., PORT=4004 vs PORT=5004 respectively within .env.development.local vs .env.production.local files respectively. Create-react-app looks for environment variables starting from closest matching .env.local files moving towards less specific ones until reaching global .env file e.g., .env.development.local``, .env.development``, .env.local``, then finally .env.
Any environment variable whose name starts with REACT_APP_ will be embedded into your app’s HTML as JavaScript constants accessible through process.env.YOUR_VARIABLE_HERE e.g., process.env.REACT_APP_API_URL=". Here’s an example illustrating above scenario:
Your app displays current URL via `Current URL:` within index.html template file generated by create react app i.e., index.html located within public folder at root directory.
Within local development environment assuming NODE_ENV equals development i.e., running locally then contents within ./.env.development.local would look something like following:
REACT_APP_URL=http:/localhost://api/vx.x/ REACT_APP_OTHER_VAR= ... ... ... ... ... PORT= ... ... ... OTHER_VAR= ... ... ... VAR= ... etc.. etc.. etc.. etc.. etc.. Within production environment assuming NODE_ENV equals production i.e., deployed then contents within ./config/.env.production would look something like following:
REACT_APP_URL=https:/www.yourwebsitehere//api/vx.x/ REACT_APP_OTHER_VAR= OTHER_VAR= VAR= ... etc.. etc.. etc.. etc.. etc.. PORT= various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... various other non REACT_APP prefixed vars go here too.... and so forth....and so forth....and so forth.... and so forth....and so forth....and so forth.... and so forth....and so forth....and so forth.... ... ... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below..... more stuff goes down below...... Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. Etc.. etc... etc... etc... ...... ...... ...... ...... ...... ...... ...... ...... ....... ...... ...... ...... ...... ...... ......... ......... ......... ......... ......... ......... ......... ........ *****END***** *****END***** *****END***** *****END***** *****END***** ****/ Note also that due security reasons node env variables cannot be accessed directly within client side javascript code i.e., anything residing outside server folder e.g., ./src , ./public ,./node_modules ,./package.json etc... Therefore any sensitive data should never be placed inside env files used by client side code i.e., anything residing outside server folder e.g., ./src , ./public ,./node_modules ,./package.json etc... Instead such sensitive data should always be placed inside env files used only by server side code i.e., anything residing inside server folder e.g., ./server/env_files . Example usage showing above scenario would involve creating separate env files per corresponding deployment environments i.e., development vs production vs testing vs staging etc... And then copying/pasting appropriate values based upon respective deployment environments being targeted e.g., copy/paste values between various env files such as ./server/.dev.env , ./server/.prod.env , ./server/.test.env , ./server/.stage.env , ./server/.other_envs.go.here.env , ../local_env_files/.local.dev.env , ../local_env_files/.local.prod.env , ../local_env_files/.local.test.env , ../local_env_files/.local.stage.env , ../local_env_files/.other_local_envs.go.here.env . Here's an example illustrating above scenario involving creating separate env files per corresponding deployment environments i.e., development vs production vs testing vs staging etc... And then copying/pasting appropriate values based upon respective deployment environments being targeted e.g., copy/pasting values between various env files such as ./server/.dev.env , ./server/.prod.env , ./server/.test.env , ./server/.stage.env , ../local_env_files/.local.dev.env , ../local_env_files/.local.prod.env , ../local_env_files/.local.test.env , ../local_env_files/.local.stage.env , Assuming NODE_ENV equals development i.e., running locally then contents within ../root_dir/local_dev_folder_path/server/dev-env-vars-example.json would look something like following:
{ "dev":{ "API_HOST":"http:/localhost:", "API_PORT": "", "API_BASE_PATH":"/api/vx.x", "SOME_OTHER_API_KEY":"keyvalue", "SOME_OTHER_API_SECRET":"secretvalue", "DATABASE_HOST":"dbhost", "DATABASE_USER":"dbuser", "DATABASE_PASSWORD":"dbpass", "DATABASE_NAME":"dbname", "DATABSE_DIALECT": "mysql", "ECHO_SQL_QUERIES": true/false, "MONGO_DB_URI": "mongodb_url_goes_here", "MONGO_DB_NAME": "", "MONGO_DB_COLLECTIONS": ["collection_names_goes_here"], "ECHO_SQL_QUERIES": true/false, "BASIC_AUTH_USER_NAME": "", "BASIC_AUTH_PASSWORD_HASHED_VALUE": "", "SOME_CUSTOM_SERVER_SIDE_VARIABLE_NAME_GOES_HERE":"some_custom_server_side_variable_value_goes_here", "SOME_CUSTOM_CLIENT_SIDE_VARIABLE_NAME_GOES_HERE":"some_custom_client_side_variable_value_goes_here", "CUSTOM_MIDDLEWARE_FUNCTION_NAME_GOES_HERE": function(req,res,next){ req.someCustomProperty='customPropertyValue'; next(); }, "CUSTOM_MONGOOSE_PLUGIN_FUNCTION_NAME_GOES_HERE": function(schema){ schema.plugin(somePluginName,{optionOne:'firstOptionValue',optionTwo:'secondOptionValue'}); }, "MIDDLEWARE_FUNCTIONS_ARRAY_GOS_HERE":[ function(req,res,next){ req.someCustomProperty='customPropertyValue'; next(); }, function(req,res,next){ res.locals.someOtherCustomProperty='anotherCustomPropertyValue'; next(); }, function(req,res,next){ req.body['foo']='bar'; next(); }, ], }, } Within production environment assuming NODE_ENV equals production i.e., deployed then contents within ../root_dir/local_prod_folder_path/server/prod-env-vars-example.json would look something like following:
{ "prod":{ "API_HOST":"http:/www.yourwebsitehere", "API_PORT": "", "API_BASE_PATH":"/api/vx.x", "SOME_OTHER_API_KEY":"keyvalue", "SOME_OTHER_API_SECRET":"secretvalue", "ECHO_SQL_QUERIES": true/false, "MONGO_DB_URI": "mongodb_url_goes_here", "MONGO_DB_NAME": "", "MONGO_DB_COLLECTIONS": ["collection_names_goes_here"], "ECHO_SQL_QUERIES": true/false, "BASIC_AUTH_USER_NAME": "", "BASIC_AUTH_PASSWORD_HASHED_VALUE": "", "SOME_CUSTOM_SERVER_SIDE_VARIABLE_NAME_GOES_HERE":"some_custom_server_side_variable_value_goes_here", "SOME_CUSTOM_CLIENT_SIDE_VARIABLE_NAME_GOES_HERE":"some_custom_client_side_variable_value_goes_here", "CUSTOM_MIDDLEWARE_FUNCTION_NAME_GOES_HERE": function(req,res,next){ req.someCustomProperty='customPropertyValue'; next(); }, "CUSTOM_MONGOOSE_PLUGIN_FUNCTION_NAME_GOES_HERE": function(schema){ schema.plugin(somePluginName,{optionOne:'firstOptionValue',optionTwo:'secondOptionValue'}); }, "MIDDLEWARE_FUNCTIONS_ARRAY_GOS_HERE":[ function(req,res,next){ req.someCustomProperty='customPropertyValue'; next(); }, function(req,res,next){ res.locals.someOtherCustomProperty='anotherCustomPropertyValue'; next(); }, function(req,res,next){ req.body['foo']='bar'; next(); }, ], }, } ***NOTE*** Note also that due security reasons node env variables cannot be accessed directly within client side javascript code i.e., anything residing outside server folder e.g., /src , /public ,/node_modules ,/package.json etc... Therefore any sensitive data should never be placed inside env files used by client side code i.e., anything residing outside server folder e.g., /src , /public ,/node_modules ,/package.json etc... Instead such sensitive data should always be placed inside env files used only by server side code i.e., anything residing inside server folder e.g., /server . Example usage showing above scenario would involve creating separate env files per corresponding deployment environments i.e., development vs production vs testing vs staging etc... And then copying/pasting appropriate values based upon respective deployment environments being targeted e.g., copy/paste values between various env files such as /server/dev-env-vars-example.json , /server/prod-env-vars-example.json , /server/test-env-vars-example.json , /server/stage-env-vars-example.json , /local_dev_folder_path/dev-env-vars-example.json , /local_prod_folder_path/prod-env-vars-example.json , /local_test_folder_path/test-env-vars-example.json , /local_stage_folder_path/stage-env-vars-example.json . Example usage showing above scenario involving creating separate env files per corresponding deployment environments i.e., development vs production vs testing vs staging etc... And then copying/pasting appropriate values based upon respective deployment environments being targeted e.g., copy/paste values between various env files such as /server/dev-env-vars-example.json , /server/prod-env-vars-example.json , /server/test-env-vars-example.json , /server/stage-env-vars-example.json , /local_dev_folder_path/dev-env-vars-example.json , /local_prod_folder_path/prod-env-vars-example.json , /local_test_folder_path/test-env-vars-example.json , /local_stage_folder_path/stage-env-vars-example.json . Assuming NODE_ENV equals development i.e., running locally then contents within ../root_dir/local_dev_folder_path/server/dev- vars-config-json-file-name-goes-here-dev-mode-value-goes-here-for-development-environment-setup-go-here-would-look-something-like-following:
*****NOTE*** Note also that due security reasons node env variables cannot be accessed directly within client side javascript code i.e., anything residing outside server folder e.g., /src , /public ,/node_modules ,/package_json.txt etc... Therefore any sensitive data should never be placed inside env-files-used-by-client-side-code-i-e,-anything-residing-outside-server-folder-e-g,-src,-public,-node_modules,-package_json.txt-and-so-on-and-so-forth type paths instead such sensitive data should always be placed inside env-files-used-only-by-server-side-code-i-e,-anything-residing-inside-server-folder-e-g,-sever type paths . Example usage showing above scenario would involve creating separate dev-vs-prod-vs-test-vs-stage-type-of-environment-specific-config-json-files-per-corresponding-deployment-environments-i-e-dev-vs-prod-vs-test-vs-stage-type-of-environment-specific-config-json-files-per-corresponding-deployment-environments-i-e-dev-vs-prod-vs-test-vs-stage-type-of-environment-specific-config-json-files-per-corresponding-deployment-environments-i-e-dev-vs-prod-vs-test-vs-stage-type-of-environment-specific-config-json-files-per-corresponding-deployment-environments-i-e-dev-vs-prod-vs-test-vs-stage-type-of-environment-specific-config-json-files-per-corresponding-deployment-environments-and-then-copy-pasting-or-parsing-or-loading-or-requiring-or-importing-or-demand-ing-or-whatever-you-want-to-call-it-the-values-based-upon-respective-deployment-environments-being-targeted-e-g-copy-pasting-or-parsing-or-loading-or-requiring-or-importing-or-demand-ing-or-whatever-you-want-to-call-it-the-values-between-various-dev-v-s-prod-v-s-test-v-s-stage-type-of-environment-specific-config-json-files-such-as-server-dev-v-s-prod-v-s-test-v-s-stage-type-of-environment-specific-config-json-file-names-gos-here-and-local_dev_v_s_local_prod_v_s_local_test_v_s_local_stage_type_of_environment_specific_config_json_file_names-gos-here-and-so-on-and-so-forth type paths . Assuming NODE_ENV equals development type value string literal constant character sequence representing running locally type setup configuration scenario involving creating separate dev- vs-prod- vs- test- vs- stage-type-of- environment- specific- config- json- files- per- corresponding- deployment- environments- i- e- dev- vs- prod- vs- test- vs- stage- type- of- environment- specific- config- json- files- per- corresponding- deployment- environments- i- e- dev- vs- prod- vs- test- vs- stage- type- of- environment- specific- environments-and-copy-pasting-values-between-various-dev-v-s-prod-v-s-test-v-s-stage-type-of-environment-specific-config-json-files-such-as-server-dev-v-s-prod-v-s-test-v-s-stage-type-of-environment-specific-config-json-file-names-gos-here-and-local_dev_v_s_local_prod_v_s_local_test_v_s_local_stage_type_of_environment_specific_config_json_file_names-gos-here-and-so-on-and-so-forth type paths : Contents within ../root_dir/local_dev_folder_path/server/config/dev.config.file.name.go.here.dev.mode