Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing backing store aspects #6

Closed
baywet opened this issue Feb 9, 2024 · 4 comments
Closed

missing backing store aspects #6

baywet opened this issue Feb 9, 2024 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@baywet
Copy link
Collaborator

baywet commented Feb 9, 2024

This doesn't need to be implemented in the language to start playing with the generation, but I thought I'd create an issue to track that.

@ricardoboss ricardoboss added enhancement New feature or request help wanted Extra attention is needed labels Feb 9, 2024
ricardoboss referenced this issue Mar 19, 2024
Implemented backing store abstractions
@ricardoboss
Copy link
Member

@baywet do you think #10 implemented enough to provide a solid foundation? Otherwise we'll just keep this open

@baywet
Copy link
Collaborator Author

baywet commented Mar 20, 2024

I've run a comparison with the dotnet implementation, here is the outline of the differences, I think a quick PR could fix all of that:

  • the singleton needs to be settable
  • backed model and backing store need to be interfaces (unless there's some dart limitation I'm not aware of?)

@ricardoboss
Copy link
Member

ricardoboss commented Mar 20, 2024

backed model and backing store need to be interfaces (unless there's some dart limitation I'm not aware of?)

Dart doesn't have interfaces. Instead it has abstract classes which you can either extend or implement. Implementing an abstract class requires you to implement all members yourself while extending it allows you to inherit already implemented members.

An abstract class that doesn't have any implemented members is what comes closest to a classical interface.

@baywet
Copy link
Collaborator Author

baywet commented Mar 20, 2024

Thanks for the explanation here. I think we're good then given the language specifics. Closing.

@baywet baywet closed this as completed Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants