-
由 Marcel Amirault 创作于We don't need to allow irregular quotes, as it could allow some tests to be avoided if the test looks for the standard style only
由 Marcel Amirault 创作于We don't need to allow irregular quotes, as it could allow some tests to be avoided if the test looks for the standard style only
代码所有者
将用户和群组指定为特定文件更改的核准人。 了解更多。
principles.md 1.09 KiB
stage: none
group: unassigned
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignmentsPrinciples
These principles ensure that your frontend contribution starts off in the right direction.
Discuss architecture before implementation
Discuss your architecture design in an issue before writing code. This helps decrease the review time and also provides good practice for writing and thinking about system design.
Be consistent
There are multiple ways of writing code to accomplish the same results. We should be as consistent as possible in how we write code across our codebases. This makes it easier for us to maintain our code across GitLab.
Improve code iteratively
Whenever you see existing code that does not follow our current style guide, update it proactively. You don't need to fix everything, but each merge request should iteratively improve our codebase, and reduce technical debt where possible.