File: template.md

package info (click to toggle)
firefox 149.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,767,760 kB
  • sloc: cpp: 7,416,064; javascript: 6,752,859; ansic: 3,774,850; python: 1,250,473; xml: 641,578; asm: 439,191; java: 186,617; sh: 56,634; makefile: 18,856; objc: 13,092; perl: 12,763; pascal: 5,960; yacc: 4,583; cs: 3,846; lex: 1,720; ruby: 1,002; php: 436; lisp: 258; awk: 105; sql: 66; sed: 53; csh: 10; exp: 6
file content (88 lines) | stat: -rw-r--r-- 2,098 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
# Template to copy

Replace the title with a clear, action-oriented name (e.g., "Adding a Toolbar
Button", "Registering JS Actors").

## Overview

Add a few paragraphs describing what this operation accomplishes and when
developers might need to do it.

## Prerequisites

List what the developer needs before starting:

- Build system set up and working
- Relevant component knowledge or documentation to review
- Any specific tools or extensions needed

## Steps

Break down the operation into clear, sequential steps. Each step should have an
action-oriented title.

### 1. [First Action Step Title]

Describe what needs to be done in this step and why it's necessary.

**Files to modify:**

- `path/to/file1.cpp`
- `path/to/file2.js`

**Code pattern:**

```cpp
// Provide a concrete example of the code to add or modify
// Include enough context to show where it should go
// Use comments to explain non-obvious parts
```

**Explanation:**

Briefly explain what this code does and how it fits into the larger system.

### 2. [Second Action Step Title]

Continue with additional steps...

**Files to modify:**

- `path/to/another/file.jsm`

**Code pattern:**

```javascript
// More example code
```

## Verification

Explain how to verify that the operation was successful:

```bash
./mach build && ./mach run
# or specific test commands
./mach test path/to/relevant/tests/
```

Describe what to look for to confirm success (e.g., "The button should appear in
the toolbar", "Check the Browser Console for the expected log message").

## Common Pitfalls

List common mistakes and their solutions:

- **Issue X**: Brief description of the problem
  - **Solution**: How to fix or avoid it

- **Issue Y**: Another common problem
  - **Solution**: The fix

## See Also

Provide links to related documentation and examples:

- [Related Component Documentation](../path/to/docs/index.rst)
- Example implementation: [Bug XXXXXX](https://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX)
- Relevant source code: {searchfox}`the ProfilesDataStoreService code <toolkit/profile/ProfilesDatastoreService.sys.mjs>`