Manuel Vila

I totally agree that the tags should be sorted by popularity (in descending order) and limited to a certain number. It should be included in the API specs.

It is indeed not very coherent. Let's make sure it is fixed in v2.

I agree that the v2 specs should not enforce the usage of a specific CSS file. A CSS file could be provided as an example, but then it'd be up...

@benjamin-thomas Indeed, a test suite for the frontend would be a nice thing to have, but I think we should wait for the v2 specs before implementing it.

@benjamin-thomas The v2 project has not started yet. We still have some work to do before we can talk about it and involve the community.

Hi @ChrisZie, I think it's better to wait for v2 which should provide a frontend reference implementation that is designed with testing in mind (e.g., relying on `data-*` attributes instead...

Hmm. The documentation is quite vague. I don't know exactly what we get with the `read:user` scope. Is it public data only? Perhaps the best thing is to try with...

I just saw that it is possible to specify no scope. It is [documented](https://docs.github.com/en/free-pro-team@latest/developers/apps/scopes-for-oauth-apps#available-scopes) as follows: > (no scope): Grants read-only access to public information (includes public user profile info,...

Hi, @mansona! It would indeed be interesting to be able to evaluate the quality of the implementations, but this seems to me rather difficult to achieve. Could you elaborate a...

I see two problems: - The performance of a frontend depends a lot on its backend. Most frontends use https://conduit.productionready.io/api as backend, which is not very performant. - Asking implementors...