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.
Should API routes be revolving around chapters
See original GitHub issue@timmyichen, @Zeko369, @nik-john, @allella I was looking at the api routes and I realized that the routes are revolving around chapters. What if an organization doesn’t have a chapter?
Just, for example, assume we have Coders.org as an organization and they don’t want any chapters under them, they host events under the organization’s name. In that case, our routes will return 404, right? I think we should include /events, /events/eventId and so on as routes. What do you all think?
_Originally posted by @vkWeb in https://github.com/freeCodeCamp/chapter/pull/162#issuecomment-554988089_
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is a good question, though I would agree with still making everything run through the Chapter-based schema, even if there’s only 1 chapter in an organization.
I feel it’s easier to hide or tweak things in the UI, for example hiding the “Chapters” menu link if there’s only 1 Chapter, then it is to have a secondary pattern / API to support single-Chapter organizations.
@allella Yes, that would be better instead of tweaking the whole API structure.