I had an index.html
file that had 1080 lines of code in it.
There were about 30 table rows in it (<tr>
) with 9 columns of data - each <td>
probably had between 2 and 15 words in it.
Those <tr>
rows amounted to about 500 lines of code.
There was a redeclared const
variable in a script tag at the bottom of the file.
I kept prompting Composer with the error message from Chrome dev tools about the redeclared variable, with the index.html
file tagged in the prompt.
Composer seemed to understand the problem and responded in its text message with the solution (to remove the redeclared variable), however:
-
It took quite a while for the ‘Accept All’ button to appear (so it looked like it was ‘thinking’)
-
After the ‘Accept All’ button appeared, there were no red/green diffs in the underlying file (
index.html
), like there normally are -
There were also no diffs visible in Composer’s ‘suggested edits’ tab
-
When I clicked on the ‘Accept All’ button the redeclared variable line was not removed
I thought it might be due to the size of the index.html
file, so I removed all those table rows.
I asked Composer to fix the issue again, and Composer was then able to present the diffs, and when I clicked the ‘Accept All’ button it successfully removed the redeclared variable line.
In regard to whether this could be due to how many ‘fast uses’ I have left - I have just purchased the pro plan, so I have 500 fast uses left.
Attached are screenshots of Composer:
-
When it couldn’t produce a diff (when the table rows were present)
-
When it could produce a diff (when the table rows were removed)
Composer - not able to create diffs
Composer - able to create diffs (after removing table rows)