-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Fix #4036 : add markdown format for output of stats script #4037
Conversation
@AdiChat rather than using subheading, the group names looked better as a top level heading, ie:- # HEADING rather than ### HEADING. C. |
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.
Doesn't the current markdown provide less information than the previous text file? I don't see any breakdowns for individual algorithms.
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.
- As a suggestion, since you are using markdown, you could also use Github emojis to indicate whether something is implemented or not. For example, if an algorithm is implemented, you could use
:white_check_mark:
(:white_check_mark:) for an algorithm which has been implemented. For algorithms not implemented, the dot looks fine.
@arnavb I like the idea. I think the ✔️ looks better. Have made pr with the change. |
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.
elm is Elm programming language
exs is Elixir interpreted file
scripts/stats.py
Outdated
"sc": "SuperCollider", | ||
"scala": "Scala", | ||
"sh": "Shell Script", | ||
"sml": "Simple Macro Language", |
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.
Standard ML
scripts/stats.py
Outdated
"rkt": "Racket", | ||
"rs": "Rust", | ||
"ruby": "Ruby", | ||
"sc": "SuperCollider", |
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.
The one file with this extension should be a .scala
file. Please fix that in this PR. SuperCollider is an audio format if I researched correctly.
"ex": "Euphoria", | ||
"exs": "Elixir", | ||
"f": "Fortran", | ||
"fs": "Visual F#", |
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.
Why no Visual for C# but Visual for F# and VB?
scripts/stats.py
Outdated
"cpp": "C++", | ||
"cr": "CRiSP", | ||
"cs": "C#", | ||
"elm": "ELM", |
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.
Caps?
scripts/stats.py
Outdated
"cs": "C#", | ||
"elm": "ELM", | ||
"erl": "Erlang", | ||
"ex": "Euphoria", |
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.
Elixir
@arnavb have made the changes. See if it can be merged. |
@AdiChat Do you think this is ready to merge? |
Yes, this looks good 👍 |
Fixes issue:
fixes #4036
Changes:
To be noted
The markdown file when viewed simply, like a txt file, wouldn't be nicely formatted or anything. Rendering it in browser(say github) or viewing in a markdown viewer would be visually pleasing as promised
How to store output in a file?
python3 scripts/stats.py -f format > location/file_name.format
Example:-
python3 stats.py -f md > ./scripts/STATS.md