question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Centralize all wikihistory.json files, maybe?

See original GitHub issue

Pros:

  • We might be able to read it all in in one sweep instead of having to open the local ./wikihistory.json file each time we’re in processFolder in the builder.
  • Fewer files for the watcher to watch.
  • Just generally lest files when navigating around in the tree.
  • Putting it all in one big file means less disk usage since individual files weigh more on disk than their size in bytes (due to all the metadata (access time, modification time, creation time, permissions))

Cons:

  • When you move a tree (or a folder for that matter) you need to mutate this one massive file each time rather than just letting it be moved.
  • Our git history won’t ever forget so now we’re going to have that in our history and as centralized files.
  • It might be hard/cumbersome when it’s so large but it’s never meant for humans to mess with anyway.
  • Just like this.allRedirects this will mean more in-memory head usage.

Notes/Ideas:

  • It might be worth checking in to git in .gz (e.g. content/files/en-us/_wikihistory.json.gz) since it’ll compress really well and it means less weight in the git repo. Also, it “sends a message” that you’re never supposed to manually edit it.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

3reactions
peterbecommented, Jun 25, 2020

The new importer is in place and I checked in all the new content in: https://github.com/mdn/yari/commit/165c30967e58a40cf578edf282c80f840a9b685b

So now you can see: No wikihistory.json Instead, it’s all in this beast

We can close this issue once I’ve updated the code that needs to rewrite that file after you rename something from the Toolbar.

0reactions
peterbecommented, Aug 12, 2020

Done.

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - Detect when a browser receives a file download
One possible solution uses JavaScript on the client. The client algorithm: Generate a random unique token. Submit the download request, and include the ......
Read more >
Wikihistory | Tor.com
But all of my searches online for the words that follow reference back to this short story (which i love – Thank you...
Read more >
History and Technology Behind the Wiki Ninja Belt Calculator ...
I had been mentioning the need for a "centralized database of everything" for TechNet Wiki activities for several years, as the number of ......
Read more >
history
extension.json changes in 1.26 === * (T99344) The extension.json schema is now versioned. All extensions and skins should set a "manifest_version" property ...
Read more >
Wikipedia:User scripts/Ranking
Script Author Last Update Active Total Navigation popups Lupin 9 Feb 2021 630 8698 Twinkle AzaToth 20 Jun 2020 541 5487 Anti‑vandal tool Lupin 22 Oct...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found