Skip to content
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: update HACKING.md with current descriptions #5507

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

tmerten
Copy link
Collaborator

@tmerten tmerten commented Jul 23, 2024

Done

  • remove old setup instructions with dotenv
  • add setup instructions for yarn/vite
  • add test running instruction
  • move site speed test running to fitting section
  • link to maas-dev-setup repo instead of manual instructions how to setup a dev env

QA steps

  • go through the instructions under # Development setup and see if you can use them to setup a MAAS UI
  • test if the updated TOC still works in the rendered (html) version of HACKING.md here in github

Screenshots

Not needed, see the file here: https://github.com/tmerten/maas-ui/blob/71fe0627eedf9e4bd5cfc79388c6e7fc296e2efe/docs/HACKING.md#set-up-a-development-container

Notes

This file needs more updating but this update should already help new users to set up and running more quickly.

- remove old setup instructions with dotenv
- add setup instructions for yarn/vite
- add test running instruction
- move site speed test running to fitting section
- link to maas-dev-setup repo instead of manual instructions how to
  setup a dev env

This file needs more updating but this update should already
help new users to set up and running more quickly.
@webteam-app
Copy link

docs/HACKING.md Outdated
- [Integration tests](#integration-tests)
- [Unit tests](#unit-tests)
- [Performance tests](#performance-tests)
- [Project conventions](#project-conventions){#toc-project-conventions}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do all of these headings have {#toc-something} afterwards? I don't think this is normal syntax, and it shows up in the file preview:

image

Copy link
Contributor

@ndv99 ndv99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great for the most part, just a few minor corrections and changes below

docs/HACKING.md Outdated

You can run MAAS-UI on your local machine assuming that you already have an instance of MAAS running somewhere that you can connect to.

In the following sections we assume that you're having your MAAS back-end running on `http:/10.10.0.30:5240`. This can easily be adapted to other IPs, names, or `https`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

double / after "http"

Suggested change
In the following sections we assume that you're having your MAAS back-end running on `http:/10.10.0.30:5240`. This can easily be adapted to other IPs, names, or `https`.
In the following sections we assume that you're having your MAAS back-end running on `http://10.10.0.30:5240`. This can easily be adapted to other IPs, names, or `https`.

docs/HACKING.md Outdated

#### Integration tests

- To run cypress end to end test run `yarn cypress-open`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- To run cypress end to end test run `yarn cypress-open`
- To run Cypress end-to-end tests run `yarn cypress-open`

docs/HACKING.md Outdated
Now you are ready to create a PR from GitHub by browsing to the branch that you just set up.

*Important tips*:
- We use conventional commits and conventional PRs and the format will be enforced by our CI. To make your life easy, you should commit using them right from the start
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- We use conventional commits and conventional PRs and the format will be enforced by our CI. To make your life easy, you should commit using them right from the start
- We use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) and conventional PRs and the format will be enforced by our CI. To make your life easy, you should commit using them right from the start. You can see a list of valid scopes [here](https://github.com/canonical/maas-ui/blob/main/.github/workflows/pr-lint.yml#L19-L37)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the links!

docs/HACKING.md Outdated

```shell
multipass shell snap-maas
```

#### LXD
### LXD

```shell
lxc exec snap-maas bash -- su ubuntu
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This command doesn't need bash to be called explicitly, you can just do lxc exec snap-maas -- su ubuntu

Copy link
Contributor

@ndv99 ndv99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@tmerten tmerten merged commit a33fd7f into canonical:main Jul 23, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants