Skip to content

Latest commit

 

History

History
211 lines (155 loc) · 10.1 KB

README.md

File metadata and controls

211 lines (155 loc) · 10.1 KB
Raw

CODAP Shared Table Plugin

Development

Copying a starter project

  1. Create a new public repository for your project (e.g. new-repository)

  2. Create a clone of the starter repo

    git clone --single-branch https://github.com/concord-consortium/starter-projects.git new-repository

  3. Update the starter repo

    First, update and run the starter project:

    cd new-repository
npm install
npm update
npm start

    Then, verify the project works by visiting localhost:8080 and checking for the words "Hello World". Also verify that the test suite still passes:

    npm run test:full

    If the updates are functional, please commit any changes to package.json or package-lock.json back to the Starter Projects repository for future use.

  4. Next, re-initialize the repo to create a new history

    rm -rf .git
git init

  5. Create an initial commit for your new project

    git add .
git commit -m "Initial commit"

  6. Push to your new repository

    git remote add origin https://github.com/concord-consortium/new-repository.git
git push -u origin main

  7. Open your new repository and update all instances of starter-projects to new-repository and Starter Projects to New Repository. Note: this will do some of the configuration for GitHub Actions deployment to S3, but you'll still need to follow the instructions here.

  8. To record the cypress tests results to the cypress dashboard service:

    • go to https://dashboard.cypress.io
    • create a new project
    • go to the settings for the project
    • in the GitHub integration section choose the GitHub repo to connect this project to
    • copy the record key, and create a secret in the GitHub repository's settings with the name CYPRESS_RECORD_KEY
    • copy the Project ID and replace the value of projectId in cypress.json
    • To enable extra Cypress to GitHub integration:
      • go to the settings of the Cypress project
      • go to the "Integrations" tab
      • select the GitHub repository

  9. To record code coverage information to codecov.io:

    • go to https://codecov.io/
    • login with your GitHub credentials
    • find your new repository
    • go to the settings for this repository and copy the CODECOV_TOKEN, and create a secret in the GitHub repository's settings.

  10. Your new repository is ready! Remove this section of the README, and follow the steps below to use it.

Initial steps

  1. Clone this repo and cd into it
  2. Run npm install to pull dependencies
  3. Run npm start to run webpack-dev-server in development mode with hot module replacement

Testing the plugin in CODAP

Currently there is no trivial way to load a plugin running on a local server with http into the online CODAP, which forces https. One simple solution is to download the latest build_[...].zip file from https://codap.concord.org/releases/zips/, extract it to a folder and run it locally. If CODAP is running on port 8080, and this project is running by default on 3000, you can go to

http://127.0.0.1:8080/static/dg/en/cert/index.html?di=http://localhost:3000

to see the plugin running in CODAP.

Create React App Readme

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about 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 the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak 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. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Run using HTTPS

Additional steps are required to run using HTTPS.

  1. install mkcert : brew install mkcert (install using Scoop or Chocolatey on Windows)
  2. Create and install the trusted CA in keychain if it doesn't already exist: mkcert -install
  3. Ensure you have a .localhost-ssl certificate directory in your home directory (create if needed, typically C:\Users\UserName on Windows) and cd into that directory
  4. Make the cert files: mkcert -cert-file localhost.pem -key-file localhost.key localhost 127.0.0.1 ::1
  5. Run npm run start:secure to run webpack-dev-server in development mode with hot module replacement

Alternately, you can run secure without certificates in Chrome:

  1. Enter chrome://flags/#allow-insecure-localhost in Chrome URL bar
  2. Change flag from disabled to enabled
  3. Run npm run start:secure:no-certs to run webpack-dev-server in development mode with hot module replacement

Building

If you want to build a local version run npm build, it will create the files in the dist folder. You do not need to build to deploy the code, that is automatic. See more info in the Deployment section below.

Notes

  1. Make sure if you are using Visual Studio Code that you use the workspace version of TypeScript. To ensure that you are open a TypeScript file in VSC and then click on the version number next to TypeScript React in the status bar and select 'Use Workspace Version' in the popup menu.

Deployment

Follow the instructions in this Guide to setup an S3 & Cloudfront distribution that can be used with GitHub actions. See also s3_deploy.sh, and ./github/ci.yml.

Production releases to S3 are based on the contents of the /dist folder and are built automatically by GitHub Actions for each branch and tag pushed to GitHub.

Branches are deployed to http://starter-projects.concord.org/branch/. If the branch name starts or ends with a number this number is stripped off.

Tags are deployed to http://starter-projects.concord.org/version/.

To deploy a production release:

  1. Increment version number in package.json
  2. Create new entry in CHANGELOG.md
  3. Run git log --pretty=oneline --reverse <last release tag>...HEAD | grep '#' | grep -v Merge and add contents (after edits if needed to CHANGELOG.md)
  4. Run npm run build
  5. Copy asset size markdown table from previous release and change sizes to match new sizes in dist
  6. Create release-<version> branch and commit changes, push to GitHub, create PR and merge
  7. Checkout main and pull
  8. Create an annotated tag for the version, of the form v[x].[y].[z], include at least the version in the tag message. On the command line this can be done with a command like git tag -a v1.2.3 -m "1.2.3 some info about this version"
  9. Push the tag to GitHub with a command like: git push origin v1.2.3.
  10. Use https://github.com/concord-consortium/starter-projects/releases to make this tag into a GitHub release.
  11. Run the release workflow to update http://starter-projects.concord.org/index.html.
    1. Navigate to the actions page in GitHub and the click the "Release" workflow. This should take you to this page: https://github.com/concord-consortium/starter-projects/actions/workflows/release.yml.
    2. Click the "Run workflow" menu button.
    3. Type in the tag name you want to release for example v1.2.3. (Note this won't work until the PR has been merged to main)
    4. Click the Run Workflow button.

Testing

Run npm test to run jest tests. Run npm run test:full to run jest and Cypress tests.

Cypress Run Options

Inside of your package.json file:

  1. --browser browser-name: define browser for running tests
  2. --group group-name: assign a group name for tests running
  3. --spec: define the spec files to run
  4. --headed: show cypress test runner GUI while running test (will exit by default when done)
  5. --no-exit: keep cypress test runner GUI open when done running
  6. --record: decide whether or not tests will have video recordings
  7. --key: specify your secret record key
  8. --reporter: specify a mocha reporter
Cypress Run Examples
  1. cypress run --browser chrome will run cypress in a chrome browser
  2. cypress run --headed --no-exit will open cypress test runner when tests begin to run, and it will remain open when tests are finished running.
  3. cypress run --spec 'cypress/integration/examples/smoke-test.js' will point to a smoke-test file rather than running all of the test files for a project.

License

Starter Projects are Copyright 2018 (c) by the Concord Consortium and is distributed under the MIT license.

See license.md for the complete license text.