@robjloranger We should leverage the changes made by abhinav in PR #19 to implement this. Most of the work will probably be in moving things around to fit our new structure where everything is broken up.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 30 2019
Nice! That's great.
May 29 2019
May 26 2019
May 24 2019
May 23 2019
May 22 2019
May 21 2019
Not sure if this is necessary -- disregard for now.
May 20 2019
May 19 2019
May 17 2019
Thanks, this all makes sense.
May 15 2019
May 14 2019
@agd Working on this now. I started off making it so that when a user is unauthenticated, all blogs and posts return a 404 (to not reveal the existence of any blog). But I'm wondering if it'd be better to send a user to the login page, instead, for better convenience. If so, we could still obscure existence of individual blogs by simply sending all routes to the login page when unauthenticated. This could be the same for the API -- all routes would just require authentication.
May 13 2019
May 12 2019
I'm going to go ahead and finish this up.
May 10 2019
May 8 2019
May 7 2019
Current status:
May 6 2019
I think we'd just redirect people to the correct route -- this would allow instance admins to set it to anything they want without modifying the app itself. For example, they could even choose a default blog to land on if they're running a multi-user instance.