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

Streamline developer documentation #6107

Merged
merged 8 commits into from
Mar 5, 2020
Merged

Streamline developer documentation #6107

merged 8 commits into from
Mar 5, 2020

Conversation

johnsaigle
Copy link
Contributor

@johnsaigle johnsaigle commented Feb 25, 2020

Brief summary of changes

Modifies some of our developer documentation to be up-to-date and less repetitive. Moves some sections around so that they are in a more appropriate place.

Resolves #4390 (With some parts of that issue being handled by #6105)

@johnsaigle johnsaigle added Cleanup PR or issue introducing/requiring at least one clean-up operation Category: Documentation PR or issue that aims to improve the documentation (test plans, wiki, comments...) labels Feb 25, 2020
@@ -1,24 +1,22 @@
# General Formatting
- Indentation should be 4 spaces instead of tabs
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this is covered differently by different files. In general this will be caught by static analysis now.

# SQL
* Prepared statements MUST be used for any statements which involve user input.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is more of a PHP thing since that's how the commands are written.

- Javascript should never be mixed with HTML or PHP code.
- Javascript should go into `modules/js/`
- Any newly written JavaScript should pass ESLint with default options.
- Compiled JavaScript should not be tracked by Git so make use of .gitignore
Copy link
Contributor Author

@johnsaigle johnsaigle Feb 25, 2020

Choose a reason for hiding this comment

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

These points are covered in the new module guide #6048 and is more appropriate there.

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
docs/CodingStandards.md Outdated Show resolved Hide resolved
Copy link
Contributor

@PapillonMcGill PapillonMcGill left a comment

Choose a reason for hiding this comment

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

Pending Travis

@driusan driusan merged commit b6b2a6f into aces:master Mar 5, 2020
@ridz1208 ridz1208 added this to the 24.0.0 milestone Apr 1, 2020
maltheism pushed a commit to maltheism/Loris that referenced this pull request Apr 7, 2020
Modifies some of our developer documentation to be up-to-date and less repetitive. Moves some sections around so that they are in a more appropriate place.

Resolves aces#4390
laemtl pushed a commit to laemtl/Loris that referenced this pull request Jun 10, 2020
Modifies some of our developer documentation to be up-to-date and less repetitive. Moves some sections around so that they are in a more appropriate place.

Resolves aces#4390
laemtl pushed a commit to laemtl/Loris that referenced this pull request Jun 16, 2020
Modifies some of our developer documentation to be up-to-date and less repetitive. Moves some sections around so that they are in a more appropriate place.

Resolves aces#4390
AlexandraLivadas pushed a commit to AlexandraLivadas/Loris that referenced this pull request Jun 29, 2021
Modifies some of our developer documentation to be up-to-date and less repetitive. Moves some sections around so that they are in a more appropriate place.

Resolves aces#4390
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Documentation PR or issue that aims to improve the documentation (test plans, wiki, comments...) Cleanup PR or issue introducing/requiring at least one clean-up operation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update "Code Review Checklist"
4 participants