You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,7 +158,7 @@ As you can see the mean duration for create 1000 rows was 144 msecs.
158
158
You can also check whether the implementation appears to be compliant to the rules:
159
159
160
160
```
161
-
npm run check keyed/vanillajs
161
+
npm run isKeyed keyed/vanillajs
162
162
```
163
163
164
164
If it finds anything it'll report an ERROR.
@@ -298,7 +298,7 @@ Contributions are very welcome. Please use the following rules:
298
298
- Webdriver-ts must be able to run the perf tests for the contribution. This means that all buttons (like "Create 1,000 rows") must have the correct id e.g. like in vanillajs. Using shadow DOM is a real pain for webdriver. The closer you can get to polymer the higher the chances I can make that contribution work.
299
299
- Don't change the ids in the index.html, since the automated benchmarking relies on those ids.
300
300
- Please push only files in your framework folder (not index.html or results.json)
301
-
-**Please make sure your implementation is validated by the test tool.** cd to webdriver-ts and invoke it with `npm run check [keyed|non-keyed]/[FrameworkName]`. It'll print an error if your framework behaves other as specified. It'll print a big ERROR explaining if it isn't happy with the implementation. Some common errors include:
301
+
-**Please make sure your implementation is validated by the test tool.** cd to webdriver-ts and invoke it with `npm run isKeyed [keyed|non-keyed]/[FrameworkName]`. It'll print an error if your framework behaves other as specified. It'll print a big ERROR explaining if it isn't happy with the implementation. Some common errors include:
302
302
- Your package.json is missing some required fields
303
303
- Incorrect classification (Keyed/NonKeyed)
304
304
- You have gzipped files in /dist (unfortunately the web server prefers these when they exist)
0 commit comments