Best Practices for Handling Entity Conflicts when Integrating Appwrite with Clean Architecture
Hello Flutter developers and Appwrite enthusiasts!
I'm currently implementing a clean architecture in my Flutter app, and I've encountered a challenge when integrating Appwrite. In my clean architecture, I have my own custom User entity and model.
The issue arises when I interact with Appwrite, which provides its own User entity. This creates a conflict where I'm getting the following error:
value of type User (where User is defined in ...appwrite...) can't be assigned to a variable of type 'User (where User is defined in ...my project...)'.
I understand this is due to the clash between the User entity from Appwrite and my custom User entity. Has anyone faced a similar issue, and what approach would you recommend to resolve this conflict while maintaining a clean architecture?
Here are a few specific questions:
1- Is it common to use the User class from Appwrite directly throughout the project, or should I prefer my custom User entity?
2- How do you handle the mapping between Appwrite's User and your custom User entity/model in your application?
3- Are there any recommended strategies for managing entities and models to keep them distinct and avoid such conflicts in a clean architecture?
I appreciate any guidance, experiences, or best practices you can share to navigate this challenge effectively.
Thank you!
About your issue of different datatypes error there are two ways :
- Change name of your custom data class
- When you import your custom User on top of your file give it a prefix then access User model using that prefix
for specific questions :
- As far as i know it depends on your usecase.
- It should be pretty simple (convert your preffered fields to a custom data model), for handling updates you can use Appwrite Functions.
