This repository was archived by the owner on Jul 2, 2024. It is now read-only.
forked from Ericsson/exchangecalendar
-
Notifications
You must be signed in to change notification settings - Fork 57
Update main project file to explain the community work and use standardized tools #70
Closed
Closed
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
5d408cd
Clean meta data and tools on the project: README, Makefile, VERSION, …
Trim 41b9e0f
fixup English typo
Trim 797ef44
README.md: add details about js-beautify (add brace option and npm lo…
Trim 1a8bc88
README.md: English style update
Trim 0dfbe93
Makefile: fix version update inside install.rdf to keep spaces correctly
Trim 007d3b9
Makefile: update beautify part (not used currently, as almost all the…
Trim 3bfa7ac
install.rdf: auto update made by make build
Trim 2d88cee
README.md: fix typo
Trim e81e22f
README.md: update patch the code paragraph (main guidelines)
Trim 31a79be
README.md: update Translation pargraph to target Transifex
Trim File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
fixup English typo
- Loading branch information
commit 41b9e0fe127067ac5e5966bf9c66a66d3dbbf17c
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think that's not correctly translate what I mean. What do you think about the following sentence to replace this one?
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.
Wouldn't it simply be better to fix all the formatting issues in one big PR by simply iterating over all JS files with a script? This will of course break all first level git-blame investigations but the positive aspect is that all future contributors won't have to worry about existing code and PRs won't be a huge mix of formatting fixes + actual semantic changes.
In other words, I think this project will proceed faster, the easier we make it to contribute.
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.
Yes, indeed, it will help.
The XML formater loose every blank line, but that's then quiet easy to add after files are well structured.
If we do that, we could also:
interface
instead ofchrome
).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.
Regarding indentation, personally I find space indentation with four spaces much easier to maintain than using tab characters.
As for the folder structure, I've replied to you in the other thread.