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

The file is too large and it is not very convenient to operate with it #4246

Open
gecube opened this issue Feb 26, 2025 · 0 comments
Open

The file is too large and it is not very convenient to operate with it #4246

gecube opened this issue Feb 26, 2025 · 0 comments

Comments

@gecube
Copy link
Contributor

gecube commented Feb 26, 2025

Good day!

The simple issue. I did not have any good tools with me and I needed to check the changes into landscape. So I opened it in browser and got something like this even on powerful laptop:

Image

It means that it is difficult to operate with the file when it's size over 500k.

I think it would be nice to split all records by some logic. Let's propose the alphabet. I think it would give almost uniform distribution and it would make changes to the file easier as maintainers ask to keep the alphabetical sort in single file. I don't see any disadvantages. Probably the only thing is that potential contributor could mess with the letters and add a new product starting from (just example) A letter in the file where only names starting from B letter are present. But it could be easily handled by automation.

So finally:

  • now we have a single landscape.yaml
  • lets' split it into landscape-a.yaml, landscape-b.yaml ... ``landscape-z.yaml` files
  • if we need to generate site, just combine programatically all files and process them as it was done before.
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

No branches or pull requests

1 participant