Coder Social home page Coder Social logo

eslint-config-uclaradio's Introduction

UCLA Radio

dependencies Status devDependencies Status Build Status styled with prettier

All of the code that powers uclaradio.com.

UCLA Radio is a Javascript application, powered by Node.js and utilizing the Express.js framework. We use MongoDB for our database and React on the front-end.

In addition to the visible site, we also have a RESTful API, which powers an internal panel for managers and DJs as well as our iOS and Android apps.

UCLA Radio is a completely student-run organization offering cultural content created by 100+ DJs. Let us know if you have any suggestions! All of the software here is written by students.

Getting Started

Running

Development

Below are the primary way we recommend for Windows and Mac users to set up the repo properly on their computer to run.
If you are wondering why you can't just clone it and be done it is because we have some extra programs that need to be downloaded in order for to run and develop the website. These include Node, MongoDB, and Yarn mainly.

The Windows set up will require the usage of Windows Subsystem for Linux in order to make downloading and installing all of these software easy. It also helps to make the environment more similar to Mac users so it is easier to get help and work together.

Mac users will need Homebrew in order to have the command terminal be able to download and install programs as if it was a complete Linux system.

Windows
  1. Install Windows Subsystem for Linux. Please download Ubuntu.
  2. Open Ubuntu and ensure git is installed by running git --version.
  3. Navigate back to the Windows c drive with cd /mnt/c/Users. (Note: if you ls and are worried about the denied permissions, that is normal because it simply means don't touch this or you might break something internally. Everything you need you have access to!)
  4. Now once you are here, cd into your own user folder. Then navigate to a directory that you want to work in. (Do not just put it in your user folder--go to your desktop or documents folder) Ex) cd Bob/Desktop and mkdir radio_stuff to make a folder/directory
  5. Run the command git clone https://github.com/uclaradio/uclaradio.git. While you wait for it download, give us some love by starring our repo.
  6. Navigate to the set up script with cd uclaradio/scripts. Then run our setup_ubuntu.sh script.
    • Wondering what this does? Basically it installs the latest versions of Node, MongoDB, and Yarn, then uses these programs to install the packages we use and set up a local database.
    • Is yarn not working? Try yarn --version and if you see 0.3# instead of 1.#.#, then run sudo apt remove cmdtest Rerun the setup script and see if it works now. More on this issue here
    • Is the setup script not running and returning an error? Try running sudo apt-get install dos2unix and then dos2unix setup_ubuntu.sh (to fix WSL formatting error).
  7. Open up another Ubuntu window by left-clicking the icon at the bottom and clicking Ubuntu. Navigate to the uclaradio repo. (To make life easier, just copy the path from the original window!)
  8. Run mongo with mongod in one Ubuntu window.
  9. Run yarn dev in the other Ubuntu window to start the server for development.
  10. Point your browser to http://localhost:3000 😍
  11. Please note that whenever you open a new ubuntu terminal you will have to navigate back to the Windows c file system. This is done as said before by going for example cd /mnt/c/Users/Bob/Desktop/uclaradio. The reason for having to do this every time you open instead of simply cloning the repo into the default WSL Ubuntu root setup is because this way you can find and open the repo with file explorer. If you'd like to edit files easily using a text/code editor, this is very crucial.
MacOS
  1. Install Homebrew.
  2. Install git by running brew install git or by installing Xcode command line tools (which includes git) with xcode-select --install.
  3. Clone our repo by running the command git clone https://github.com/uclaradio/uclaradio.git. While you wait for it download, give us some love by starring our repo.
  4. Navigate to the scripts directory and run our setup.sh script.
    • Wondering what this does? Basically it installs the latest versions of Node, MongoDB, and Yarn, then uses these programs to install the packages we use and set up a local database.
  5. Run nodenv init, and follow the instructions it tells you.
    • If you have a problem that looks like error: unknown type name 'uint64_t' uint64_t ri_user_time; you're going to need to rename your /usr/local/include folder to something else. I used usr/local/include_old. This solution is from the following issue https://github.com/cython/cython/issues/2009 if you're interested in reading more about the error.
  6. Run mongo with mongod.
  7. Run yarn dev to start the server for development.
  8. Point your browser to http://localhost:3000 😍

Production

  • Make sure all packages are installed with yarn.
  • Run node bin/www prod to start the server for production (will require HTTPS and listen on port 80).

Getting Started

Structure

uclaradio/
β”œβ”€β”€ LICENSE.md
β”œβ”€β”€ README.md
β”œβ”€β”€ app                       # Backend code
β”‚Β Β  β”œβ”€β”€ app.js                # The main server file
β”‚Β Β  β”œβ”€β”€ database/             #
β”‚Β Β  β”œβ”€β”€ routes/               #
β”‚Β Β  └── services/             #
β”œβ”€β”€ bin
β”‚Β Β  └── www                   # The command to run node
β”œβ”€β”€ client                    # Frontend code
β”‚Β Β  β”œβ”€β”€ public/               #
β”‚Β Β  β”œβ”€β”€ react/                # React files
β”‚Β Β  └── views/                # Jade templates
β”œβ”€β”€ defaultPasswords.json
β”œβ”€β”€ package.json
β”œβ”€β”€ scripts/                  # Scripts to set things up
β”œβ”€β”€ webpack.config.babel.js
└── yarn.lock

Requirements for new code

As a student-run organization, UCLA Radio is especially liable to technical debt. We have some goals for cleaning up our codebase in the future, but most importantly new code should:

  • Have new front-end pages in React. We prefer using a front-end framework with an API to complicated templates.
  • Delete files that are not used anymore. It's okay, get rid of clutter.
  • Follow an organized structure. Put things in the right directories.

We accept changes from both radio web members and outside contributors. Please note both our contributing guidelines and code of conduct before making a pull request. Want to join radio? We accept applications every quarter.

License

All of the code here is released under the GNU AGPL 3.0 License, which basically means you can do anything you want with the code here as long as you attribute us and release what you make under the same license. If you've made something cool with our code or are interested in relicensing our code, let us know; we'd love to hear what you made!

eslint-config-uclaradio's People

Contributors

greenkeeper[bot] avatar nathanmsmith avatar

Watchers

 avatar  avatar  avatar  avatar

eslint-config-uclaradio's Issues

An in-range update of standard-version is breaking the build 🚨

Version 4.4.0 of standard-version was just published.

Branch Build failing 🚨
Dependency standard-version
Current Version 4.3.0
Type devDependency

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

standard-version 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 8 commits.

  • e5c99f6 chore(release): 4.4.0
  • 04c68a8 chore: npm audit (#244)
  • ba4e7f6 feat: add prerelease lifecycle script hook (closes #217) (#234)
  • b4ed4f9 fix: show full tag name in checkpoint (#241)
  • fbfdf5e doc : added an example of a postcommit hook (#232)
  • 371d992 feat: manifest.json support (#236)
  • 6dac27b docs: add title to LICENSE.txt (#238)
  • a56c7ac fix: use tagPrefix in CHANGELOG lifecycle step (#243)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-prettier is breaking the build 🚨

Version 2.6.1 of eslint-plugin-prettier was just published.

Branch Build failing 🚨
Dependency [eslint-plugin-prettier](https://github.com/prettier/eslint-plugin-prettier)
Current Version 2.6.0
Type dependency

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

eslint-plugin-prettier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits.

  • 1c41c41 Build: update package.json and changelog for v2.6.1
  • 0b04dd3 Fix: respect editorconfig (#92)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-react is breaking the build 🚨

Version 7.8.0 of eslint-plugin-react was just published.

Branch Build failing 🚨
Dependency eslint-plugin-react
Current Version 7.7.0
Type dependency

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

eslint-plugin-react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v7.8.0

Added

  • Add support for fragments to react-in-jsx-scope (#1758)
  • Add support for Flow generic PropType to require-default-props (#1724 @Miziak)
  • Add component whitelist option to forbid-component-props (#1732 @ThiefMaster)
  • Add support for React 16.3 lifecycle methods to no-unused-prop-types (#1681 @bvaughn)
  • Add support for React 16.3 lifecycle methods to sort-comp (#1767 @joe-denea)
  • Add support for React 16.3 lifecycle methods to no-typos
  • Add support for prevState and nextState to no-unused-state (#1759)
  • Add warnings for componentWillMount, componentWillReceiveProps and componentWillUpdate lifecycle methods in no-deprecated (#1750 @sergei-startsev)

Fixed

Changed

Commits

The new version differs by 65 commits.

  • fb7411d Update CHANGELOG and bump version
  • b5865e8 Replace static status badge by a dynamic one
  • 79f32b1 Fix Code Climate badge in README
  • ab803e5 Update CHANGELOG and bump version
  • b26d1cc Add prevState and nextState support to no-unused-state (fixes #1759)
  • 3aac310 Add support for React 16.3 lifecycle methods to no-typos
  • 5f3f04f Merge pull request #1783 from chentsulin/patch-1
  • 26dc5a6 fix typo containing
  • 9519938 Add getSnapshotBeforeUpdate support to no-unused-prop-types (fixes #1751)
  • d51b0cc Add fragment support to react-in-jsx-scope (fixes #1758)
  • fb7ce94 Merge pull request #1771 from joe-denea/master
  • 230b0ad [Tests] fix appveyor
  • 768013e Add support for React 16.3 lifecycle methods
  • d68ef96 Merge pull request #1750 from sergei-startsev/no-deprecated
  • 8973758 [Tests] fix linting errors

There are 65 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-jsx-a11y is breaking the build 🚨

Version 6.1.0 of eslint-plugin-jsx-a11y was just published.

Branch Build failing 🚨
Dependency eslint-plugin-jsx-a11y
Current Version 6.0.3
Type dependency

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

eslint-plugin-jsx-a11y is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes Support eslint v5

6.1.0 / 2018-06-26

  • [new] Support for eslint v5, #451
  • [new] aria-query updated to latest version
  • [new] eslint-config-airbnb-base updated to the latest version
  • [deprecate] The rule label-has-for is deprecated and replaced with label-has-associated-control
  • [fix] heading-has-content updated to work with custom components, #431
  • [fix] aria-errormessage prop is now a valid ARIA property, #424
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of greenkeeper-lockfile is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.13.3 of greenkeeper-lockfile was just published.

Branch Build failing 🚨
Dependency greenkeeper-lockfile
Current Version 1.13.2
Type devDependency

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

greenkeeper-lockfile 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.13.3

1.13.3 (2018-02-28)

Bug Fixes

  • Use build number from env on Jenkins (d2b51fb)
Commits

The new version differs by 3 commits.

  • d2b51fb fix: Use build number from env on Jenkins
  • 3af5bf9 chore(package): update lockfile
  • 0371975 chore(package): update standard to version 11.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.9.0 of eslint-plugin-import was just published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.8.0
Type dependency

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

eslint-plugin-import is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 101 commits.

  • 180d71a bump plugin to v2.9.0
  • 0231c78 Merge pull request #1026 from isiahmeadows/patch-1
  • ae5a031 Missed a link
  • 5b0777d Add no-default-export + docs/tests (#936)
  • ff3d883 Merge pull request #1025 from patrick-steele-idem/update-dependencies
  • 654d284 Merge pull request #1024 from patrick-steele-idem/issue-1023
  • 9b20a78 Upgraded "find-root" and "lodash.get" for the webpack resolver
  • 8778d7c Fixes #1023 - Load exceptions in user resolvers are not reported
  • 91cfd6d Merge pull request #1022 from nevir/patch-1
  • 0e729c7 no-self-import is unreleased
  • 219a8d2 Merge pull request #1012 from silvenon/extensions-export
  • ab49972 Support export declarations in extensions rule
  • 3268a82 Merge pull request #1010 from silvenon/extensions
  • fdcd4d9 Add a .coffee test proving extension resolve order
  • bc50394 Merge pull request #1009 from silvenon/extensions

There are 101 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-config-prettier is breaking the build 🚨

Version 2.10.0 of eslint-config-prettier was just published.

Branch Build failing 🚨
Dependency eslint-config-prettier
Current Version 2.9.0
Type dependency

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

eslint-config-prettier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 4 commits.

  • 9f42779 eslint-config-prettier v2.10.0
  • 7a95862 Add more eslint-plugin-react rules
  • becbdf3 Add flowtype/boolean-style
  • 0f13166 Fix wording in readme

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.