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: CONTRIBUTING.md
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,31 @@ yet in the issue tracker, start by opening an issue. Thanks!
24
24
1.`grind` is needed to run dartdoc integration tests, see installed via `pub global activate grinder`.
25
25
2. When a change is user-facing, please add a new entry to the [changelog](https://github.com/dart-lang/dartdoc/blob/master/CHANGELOG.md)
26
26
3. Please include a test for your change. `dartdoc` has both `package:test`-style unittests as well as integration tests. To run the unittests, use `dart test/all.dart`. Most changes can be tested via a unittest, but some require modifying the [test_package](https://github.com/dart-lang/dartdoc/tree/master/testing/test_package) and regenerating its docs via `grind update-test-package-docs`.
27
-
4. Be sure to format your Dart code using `dartfmt -w`, otherwise travis will complain.
28
-
5. Post your change via a pull request for review and integration!
27
+
4. For major changes, run `grind compare-sdk-warnings` and include the summary results in your pull request.
28
+
5. Be sure to format your Dart code using `dartfmt -w`, otherwise travis will complain.
29
+
6. Post your change via a pull request for review and integration!
30
+
31
+
## Testing
32
+
33
+
dartdoc has a number of grinder utility methods that can be used to check for behavior changes
34
+
or try out your change on arbitrary packages.
35
+
36
+
```bash
37
+
# Serve the latest version of the given package locally on port 9000.
0 commit comments