Skip to content

Improvement/GDL-12-add-prettier-config#211

Open
benzekrimaha wants to merge 4 commits intodevelopment/8.2from
improvement/GDL-12-add-new-prettier-config
Open

Improvement/GDL-12-add-prettier-config#211
benzekrimaha wants to merge 4 commits intodevelopment/8.2from
improvement/GDL-12-add-new-prettier-config

Conversation

@benzekrimaha
Copy link

@benzekrimaha benzekrimaha commented Mar 9, 2026

Issue: GL-12

@bert-e
Copy link
Contributor

bert-e commented Mar 9, 2026

Hello benzekrimaha,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@benzekrimaha benzekrimaha force-pushed the improvement/GDL-12-add-new-prettier-config branch from 42093e9 to 6749be6 Compare March 9, 2026 15:44
This commit defines line ending/newline defaults and per-file indentation rules so local editors match the shared Prettier policy across JS/TS, JSON, YAML, Markdown, and Makefiles.
Issue: GDL-12
This commit upldate the documentation to explain the new Prettier baseline,
recommended adoption steps, and editor alignment so downstream repositories
can import and apply the config consistently.
Issue: GDL-12
@benzekrimaha benzekrimaha force-pushed the improvement/GDL-12-add-new-prettier-config branch from 6749be6 to 2fb532e Compare March 9, 2026 15:47
@scality scality deleted a comment from bert-e Mar 9, 2026
@bert-e
Copy link
Contributor

bert-e commented Mar 9, 2026

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@benzekrimaha benzekrimaha marked this pull request as ready for review March 9, 2026 15:50
@benzekrimaha benzekrimaha changed the title Improvement/gdl 12 add new prettier config Improvement/GDL-12-add-prettier-config Mar 9, 2026
.editorconfig Outdated
indent_style = space
indent_size = 4

[Makefile]
Copy link
Contributor

@francoisferrand francoisferrand Mar 9, 2026

Choose a reason for hiding this comment

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

Also applies to golang (which we have in our code base, and would thus be affected by a .editorconfig file)

Suggested change
[Makefile]
[{Makefile,*.go,go.*}]

indent_size = 4

[Makefile]
indent_style = tab
Copy link
Contributor

@francoisferrand francoisferrand Mar 9, 2026

Choose a reason for hiding this comment

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

Should also specify indent_size (for alignment) ?

Suggested change
indent_style = tab
indent_style = tab
indent_size = 4

charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true
Copy link
Contributor

@francoisferrand francoisferrand Mar 9, 2026

Choose a reason for hiding this comment

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

Suggested change
trim_trailing_whitespace = true
trim_trailing_whitespace = true
max_line_length = 120

Copy link
Contributor

Choose a reason for hiding this comment

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

(or maybe should only be set for javascript files, e.g. around line 11)

.editorconfig Outdated
Comment on lines +10 to +11
indent_style = space
indent_size = 4
Copy link
Contributor

@francoisferrand francoisferrand Mar 9, 2026

Choose a reason for hiding this comment

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

nit: instead of repeating indent style & size for each kind of file, we may put this in the * block and override it only where needed (to reduce duplication)

README.md Outdated
}
```

Projects are free to override options locally (for example `tabWidth` or
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
Projects are free to override options locally (for example `tabWidth` or
Projects may override options locally (for example `tabWidth` or

README.md Outdated
Comment on lines +52 to +54
Node.js codebases. YAML defaults to 2-space indentation, JSON and Markdown to
4-space indentation, and Markdown prose is left un-reflowed by default
(`proseWrap: 'preserve'`) to avoid noisy diffs in existing documentation.
Copy link
Contributor

Choose a reason for hiding this comment

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

this paraphrases the content of the config, so does not add much value but creates a risk of being outdated: best leave it out?

Suggested change
Node.js codebases. YAML defaults to 2-space indentation, JSON and Markdown to
4-space indentation, and Markdown prose is left un-reflowed by default
(`proseWrap: 'preserve'`) to avoid noisy diffs in existing documentation.
Node.js codebases.

README.md Outdated

## Editor configuration

For a consistent editor experience, you can copy or adapt the `.editorconfig`
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
For a consistent editor experience, you can copy or adapt the `.editorconfig`
For a consistent editor experience, you can copy the `.editorconfig`

4-space indentation, and Markdown prose is left un-reflowed by default
(`proseWrap: 'preserve'`) to avoid noisy diffs in existing documentation.

## Editor configuration
Copy link
Contributor

@francoisferrand francoisferrand Mar 9, 2026

Choose a reason for hiding this comment

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

do we actually need (and recommend) using editorconfig ?

  • AFAIK there is currently not much problem, editors (like vscode) already follow the code appropriately
  • since we need to copy the file, it creates an independent copy, which may diverge over time... and we have no way to check consistency with the "original" in Guidelines (or should we have a postscript to copy the .editorconfig from guideline module to the root of the repo importing it?)

→ either it is needed, and we should recommend to use it ("For a consistent editor experience, you should copy the .editorconfig...)
→ or it is not needed, and there is no need to mention it

Reduce editorconfig duplication, add Go/Makefile tab alignment and max line length, and tighten README wording to avoid config drift and clarify .editorconfig recommendation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants