Skip to content
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

Rewrite docs linter, ease JSFiddle request debugging #2904

Merged
merged 3 commits into from
Sep 2, 2024

Conversation

dead-claudia
Copy link
Member

@dead-claudia dead-claudia commented Sep 1, 2024

Description

I'll defer to the commit descriptions. They're self-descriptive.

The first diff is quite large.

Motivation and Context

The caching I felt was unnecessary considering how uncommonly it's used. Also, it simplified the rest of the partial rewrite.

How Has This Been Tested?

I tested it locally. Now, the real test is what happens here.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation change

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have updated docs/changelog.md

@dead-claudia
Copy link
Member Author

Admittedly, the request content type detection is inefficient. But it's good enough, and I wanted to do at least minimal encoding manipulation on it.

Oh, and it also follows redirects and allows for retries.

@dead-claudia dead-claudia force-pushed the jsfiddle-debug branch 3 times, most recently from b354f31 to 92b4a51 Compare September 2, 2024 13:59
@dead-claudia dead-claudia changed the title Partially rewrite docs linter, ease JSFiddle request debugging Rewrite docs linter, ease JSFiddle request debugging Sep 2, 2024
@dead-claudia
Copy link
Member Author

Okay, it appears #2898 is just a flake. Will tack one extra commit to fix the outstanding issues and remove the CI debug crud, then I'll merge.

1. I want to set the stage to deal with MithrilJS#2898 properly.
2. `request` was deprecated years ago. Decided that it's better to just
   move to native Node.js APIs in its place.
3. `glob` was outdated, and it's easier to just toss it than to upgrade
   across a major version.
4. I switched to using Marked's "lexer" directly so I'm not fussing
   with the complexity of renderers. This of course necessitated a more
   complex file processor as its "lexer" is really an AST parser.

I also decided to go a few steps further:
- Drop the cache to simplify everything. I might reverse this later,
  but just caching URLs per-page should be enough to prevent the world
  from crashing down.
- Drop some more dependencies, so I don't have to come back to this
  later nearly as quickly.
- Upgrade to a more modern language version in the scripts.
- Update Marked. It was super outdated.
- Add line and column numbers to the warnings. That took quite a bit of
  work, thanks to a missing Marked feature plus a bug in Marked.
@dead-claudia dead-claudia merged commit 620679a into MithrilJS:next Sep 2, 2024
7 checks passed
@dead-claudia dead-claudia deleted the jsfiddle-debug branch September 2, 2024 14:08
This was referenced Sep 17, 2024
@JAForbes JAForbes mentioned this pull request Sep 24, 2024
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.

1 participant