Skip to content

Commit b9f7d7b

Browse files
robertleeplummerjrrobertleeplummerjr
committed
fix: Move varWarn to and unit test that all FunctionNode's use it
fix: Test that getExtension is set to be able to use on TravisCI fix: Remove wraparound, is no longer being used anywhere fix: add getMemoryOptimizedPackedTextureSize to string kernel fix: Remove console.log() usage fix: Move addFunction functionality into new utils method `functionToIFunction` fix: Fix mergeSettings to use `functions` settings and use `functionToIFunction` fix: Remove the spread operator for now, for compatibility with safari fix: Add typings for `setFunctions` fix; Failing unit tests for sarafi feat: Add CONTRIBUTING.md feat: Add ISSUE_TEMPLATE.md fix: Remove typescript from dependencies fix: Document, document, document fix: Bump version and build
1 parent 6c055ca commit b9f7d7b

36 files changed

Lines changed: 981 additions & 637 deletions

‎CONTRIBUTING.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
Thanks for taking the time to contribute to gpu.js. Follow these guidelines to make the process smoother:
2+
3+
1. One feature per pull request. Each PR should have one focus, and all the code changes should be supporting that one feature or bug fix. Using a [separate branch](https://guides.github.com/introduction/flow/index.html) for each feature should help you manage developing multiple features at once.
4+
5+
2. Follow the style of the file when it comes to syntax like curly braces and indents.
6+
7+
3. Add a test for the feature or fix, if possible. See the `test` directory for existing tests and README describing how to run these tests.

‎ISSUE_TEMPLATE.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
<!-- If you don't mind add a fun gif or meme, but no pressure -->
2+
![A GIF or MEME to give some spice of the internet](url)
3+
4+
## *What* is wrong?
5+
<!-- Ex. run takes really long -->
6+
7+
## *Where* does it happen?
8+
<!-- Ex. In GPU.js when trying to run a math function in node.js on my mac -->
9+
10+
## *How* do we replicate the issue?
11+
<!-- Please be specific as possible. Use dashes (-) or numbers (1.) to create a list of steps -->
12+
13+
## *How* important is this (1-5)?
14+
<!-- On a scale from 1-5 where 5 is the most important how would you rate it? -->
15+
16+
## Expected behavior (i.e. solution)
17+
<!-- What do you think should have happened? -->
18+
19+
20+
## Other Comments

0 commit comments

Comments
 (0)