-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: fix missing links and add consistency #6177
Conversation
d461a1f
to
52e1435
Compare
0386661
to
1e8c407
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thank you @hacksparrow
docs/site/Concepts.md
Outdated
@@ -13,24 +14,24 @@ responsibilities for typical API and/or Microservice applications. | |||
|
|||
- [**Application**](Application.md): The central class for setting up all of | |||
your module’s components, controllers, servers and bindings. The Application | |||
class extends [Context](Context.md) and provides the controls for starting and | |||
stopping its associated servers. | |||
class extends [Context](./Context.md) and provides the controls for starting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick, it's ok to keep as Context.md
for consistency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I had updated to relative paths, but undid it after seeing a lot more of non-breaking non-relative paths. It would be inconsistent to update only some of them in this PR; and I did not want to get into updating everything, you never know what new problems might be encountered. I wanted to make this PR a quick one. Let's keep "use of relative paths on all doc pages" as a task for another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I got what you mean. Updating.
Fixed missing links and added consistency. Signed-off-by: Yaapa Hage <[email protected]>
1e8c407
to
02fa0ab
Compare
Addresses #6176.
There were some inconsistencies in use of plurals, causing the links to fail. I have also renamed the title "Behind the scenes" to "Concepts", as it should be.
On my local machine, after running
npm run docs:prepare
, I could not start the server withnpm run docs:start
due to this error:I had to comment out
{% include readmes/loopback-example-angular.md %}
ondocs/_preview/pages/readmes/loopback-next/sandbox/loopback.io/README.md
to get it working.I don't know if the remote doc server will encounter the same error or not. If it is going to encounter the same error, land this only after fixing that issue first.
Checklist
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈