From 323680f1835b49254ca4eed0fb4bdba65f7b1644 Mon Sep 17 00:00:00 2001 From: Eric Schultz Date: Thu, 7 Jun 2018 11:04:41 -0500 Subject: [PATCH 1/2] Add a typescript style instruction --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 4aba504c..508e634f 100644 --- a/README.md +++ b/README.md @@ -181,6 +181,7 @@ For this to work though, the following characteristics must be true: #### New frontend code - All new front end code should be written in Typescript and React (using TSX files). Please use the React Generators for creation. +- 2 spaces for tabs #### Legacy Javascript - 2 spaces for tabs From 5e8b366087bd9b04db8231f782ea75086aa12c20 Mon Sep 17 00:00:00 2001 From: Eric Schultz Date: Thu, 7 Jun 2018 11:06:25 -0500 Subject: [PATCH 2/2] Clarify the CCS requirements --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 508e634f..1f87a915 100644 --- a/README.md +++ b/README.md @@ -160,15 +160,15 @@ This generator creates a basic Typescript module along with a test file. **Note: This is not legal advice and provides a suggestion which may be compliant. You should talk with your legal counsel if you have questions or concerns with how to comply with the various licenses of Houdini** -Providing the complete, corresponding source code (CCS) of your project to comply with the license of Houdini. There are two methods for doing so right now: +Providing the complete, corresponding source code (CCS) of your project is a requirement of some of the licensed used by Houdini. There are two methods for doing so right now: 1. Providing a tarball of the current running code 2. Providing a link to Github where the code is pulled from -The easiest method is to provide a tarball. Houdini automatically provides a link on the Terms & Privacy page. +The easiest method is to provide a tarball. Houdini automatically provides a link on the Terms & Privacy page which generates a tarball for the current running code at runtime. For this to work though, the following characteristics must be true: -* Your have to have any changes you made to the project in `HEAD` in your git repository +* Your have to have committed any changes you made to the project in `HEAD` in your git repository * The `.git` folder for your repository must be a direct subfolder of your `$RAILS_ROOT` * Your web server must be able to run `git archive`.