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

feat: SchemaRecord stage-1, never write a Model again #8845

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

runspired
Copy link
Contributor

@runspired runspired commented Sep 5, 2023

Its Happening.

(Note: no implementation here yet, just all the infra and the README). This PR will explore the final design for the associated RFCs (we expect a minimum of 3 RFCs to achieve this)

stage-1: feature compat with @ember-data/model
stage-2: feature compat with ModelFragments
stage-3: deeply nested inverse: null relationships
stage-4: deeply nested managed inverses, partial record support

TODO Stage 1:

  • Implement Store and Cache forking for JSON:API Cache (already RFC'd)
  • Implement Improved Schema Service (Map, simpler field defs, registerDerivation, registerTransform, addSchemas)
    • RFC Improved SchemaService
  • Implement Paginated Collection Relationships
    • RFC Paginated Relationships
  • Implement attribute, resource, collection behaviors
    • RFC SchemaRecord

@runspired runspired added 🎯 canary PR is targeting canary (default) 🏷️ feat This PR introduces a new feature labels Sep 5, 2023
@runspired runspired changed the title feat: SchemaRecord, never write a Model again feat: SchemaRecord stage-1, never write a Model again Sep 5, 2023
@runspired runspired self-assigned this Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎯 canary PR is targeting canary (default) 🏷️ feat This PR introduces a new feature
Projects
Status: in progress
Development

Successfully merging this pull request may close these issues.

1 participant