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

build.pldb.com refresh #53

Closed
breck7 opened this issue Sep 2, 2022 · 3 comments
Closed

build.pldb.com refresh #53

breck7 opened this issue Sep 2, 2022 · 3 comments

Comments

@breck7
Copy link
Owner

breck7 commented Sep 2, 2022

We need to make it easier for people to add content:
73706e5

  • when you add a subreddit the reddit importer should run and update immediately
  • we should have autocomplete for the language ids
@breck7
Copy link
Owner Author

breck7 commented Sep 4, 2022

Here are some things we need:

  • MUCH faster save. DONE.
  • On save pldb.com should be updated
  • Run crawlers on edit server
  • Show real time error reporting. DONE.

@breck7 breck7 changed the title improve Editor documentation, error checking, and run importers on edit server Editor refresh Sep 4, 2022
@breck7 breck7 changed the title Editor refresh edit.pldb.com refresh Sep 4, 2022
@breck7
Copy link
Owner Author

breck7 commented Sep 4, 2022

I just added - Should show which fields are missing for a language and sort those missing fields by importance in commit ab7af16

@ghost
Copy link

ghost commented Jan 16, 2023

@breck7 : May be there could be a lst-rprts.pldb.com a place where lists, reports and their statics could also be mentioned, like a dashboard/reporting tool for knowing, if the data store requires
(a)The need to run a crawler ?
(b) List statics for data base seeding ( a lot of build time messages could be piped there, along with completion statics, etc).

if npm run build, npm run tests generate a scroll file with the information it would be an awesome addition.

npm run crawlers could update the scroll file too.

Right now all these exists, spread in various places, unless people know where to look, they could be confused.

It could even help ohayo project with data validation tool prototype, before data is visualized (only if people use tree-notation to store data, of course)

Your thoughts ?

@breck7 breck7 self-assigned this Feb 10, 2023
@breck7 breck7 closed this as completed May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant