upgrading minor challenge issues across the board with a batch script
See original GitHub issueformatting challenges has been updated (#34747) so <br>
tags should no longer be required. Can anyone think of edge cases where a <br>
may still be required?
variables declared with var
could also be changed to const - or let if there is (re)assignment in the body.
@ezioda004 pointed out there are challenges in ES6 section specifically aimed at changing var to const/let so miss that section.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Batch Script - Quick Guide
Batch Script - Quick Guide, Batch Script is incorporated to automate command ... This batch command moves files or directories between directories.
Read more >How to Use Windows Batch File Commands to Automate ...
1. Open Multiple Programs Using a Batch File. If you have a list of programs you open each time you fire up your...
Read more >World Economic Outlook Update, July 2022: Gloomy and ...
A tentative recovery in 2021 has been followed by increasingly gloomy developments in 2022 as risks began to materialize.
Read more >Tuning and Profiling Logstash Performance
The Elasticsearch output, for example, issues bulk requests for each batch received. Tuning the pipeline.batch.size setting adjusts the size of bulk ...
Read more >Known issues with PaperCut MF, NG, Hive ...
This page lists all Known Issues across PaperCut products and includes ... seen in the server.log in a small number of customers after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I second this recommendation. There are a couple of PRs we are going to wait on creating (mass find/replace) PRs which affect 100s of files, so we have decided to wait until we get below 500 open PRs to avoid other PRs stacking up behind them as we clear through eariler PRs to prevent mass chaining of merge conflicts.
I think it is a great idea and some of this logic could be added to the Probot to catch these kinds of things when new PRs are created. When it gets closer to time to create the actual PR, we should revisit this issue to make sure we have everything covered.
Just to clarify - I meant, the challenges before the ES6 challenge Explore Differences Between the var and let Keywords should not be modified with
let/const
.