phui backend #9
phui backend #9
Conversation
There was a problem hiding this comment.
couple of minor nitpicks and questions. overarching question is if we're refactoring for pocketbase should we just bite the bullet and replace Strapi with PhenoBackendProvider or something for the specific implementation since it's with Pocketbase instead of Strapi now? I don't feel super strongly about it but since this is a refactor I figured it could be a good time....
| @@ -32,7 +31,7 @@ class RenderLayoutState extends State<RenderLayout> { | |||
| @override | |||
| void initState() { | |||
| super.initState(); | |||
| var dataProvider = StrapiDataProvider(sourceId: Strapi().server, category: widget.category); | |||
| var dataProvider = StrapiDataProvider(sourceId: Strapi().server, category: widget.tagId); | |||
There was a problem hiding this comment.
super nitpicky but if this isn't strapi anymore should we rename the dataprovider to a more generic naming convention?
There was a problem hiding this comment.
what's the purpose of these webview changes exactly? webviews seemed to work on iOS and I thought (although maybe I am misremembering) they worked on macOS as well?
No description provided.