Coder Social home page Coder Social logo

Comments (5)

ykdojo avatar ykdojo commented on September 24, 2024

An idea about how we might be able to implement this:

What if, every time a user loads one of the pages for an organization, we load all the repo names onto the client? If we're worried about the API limit, we can cache this list in SB. (We won't necessarily have to show everything on the UI at once - that can be determined by the client-side code.)

That way, filtering/searching through the repo names will be really quick. With this approach, we can solve #41 at the same time, too. Plus, having an array of 2000 short strings (and maybe their star counts) loaded on the client isn't going to be that expensive.

from repository.surf.

ykdojo avatar ykdojo commented on September 24, 2024

Another idea:

Limit the number of repos shown to 100 by default (the 100 most starred ones). Then, if someone wants to see more, get them to pay a bit 😛

from repository.surf.

kiwicopple avatar kiwicopple commented on September 24, 2024

Limit the number of repos shown to 100 by default (the 100 most starred ones). Then, if someone wants to see more, get them to pay a bit 😛

Agree with this approach!

from repository.surf.

kiwicopple avatar kiwicopple commented on September 24, 2024

Just thinking about structuring the site too:

Perhaps we also do away with the /[org]/[repo] and the sidebar just becomes a "filter bar."
Essentially there is only one page (/[org]), which might have some filter parameters appended to the URL:

  • repository.surf/supabase: shows all repos
  • repository.surf/supabase?r=supabase,infrastructure,supabase-js: only some selected.

The URL might get very long though - may be better not to append the filters to the URL (but it would make chart embedding easier).

Just a suggestion

from repository.surf.

ykdojo avatar ykdojo commented on September 24, 2024

The URL might get very long though - may be better not to append the filters to the URL (but it would make chart embedding easier).

With this approach, maybe we can store a map/table of a shortened URL parameter to a list of selected repos in SB?

So the table could look like:

organization (primary key), uuid (primary key), selected_repos (json)
supabase, j309j2j, ['supabase', 'infrastructure', 'supabase-js']
supabase, oj122j0, ['supabase', 'supabase-js']

And the corresponding URLs:

  • repository.surf/supabase?r=j309j2j
  • repository.surf/supabase?r=oj122j0

from repository.surf.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.