Skip to content

Commit

Permalink
remove remaining tocs
Browse files Browse the repository at this point in the history
  • Loading branch information
ravern committed Nov 3, 2023
1 parent 358a70c commit 080c2a3
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 7 deletions.
4 changes: 0 additions & 4 deletions docs/tutorials/RemovingFields.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,6 @@ This tutorial aims to give you some practice on such a code 'removal' activity b
However, if you have no such prior knowledge, removing a field can take a quite a bit of detective work. This tutorial takes you through that process. **At least have a read even if you don't actually do the steps yourself.**
</div>


* Table of Contents
{:toc}

## Safely deleting `Address`

IntelliJ IDEA provides a refactoring tool that can identify *most* parts of a removal easily. Let’s try to use it as much as we can.
Expand Down
3 changes: 0 additions & 3 deletions docs/tutorials/TracingCode.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,6 @@ title: "Tutorial: Tracing code"
When trying to understand an unfamiliar code base, one common strategy used is to trace some representative execution path through the code base. One easy way to trace an execution path is to use a debugger to step through the code. In this tutorial, you will be using the IntelliJ IDEA’s debugger to trace the execution path of a specific user command.

* Table of Contents
{:toc}

## Before we start

Before we jump into the code, it is useful to get an idea of the overall structure and the high-level behavior of the application. This is provided in the 'Architecture' section of the developer guide. In particular, the architecture diagram (reproduced below), tells us that the App consists of several components.
Expand Down

0 comments on commit 080c2a3

Please sign in to comment.