Skip to content

Relation remote methods should not be defined using a resolver #533

Closed

Description

@ritch

This means all relation remote methods will be defined every time sharedClass.methods() is called. I'd like to remove this and instead implement it in a hook that runs after the model is setup. This will make the list of sharedClass.methods() static and make things like sharedClass.find(...).shared = false work for all cases.

Here is a proposal for that hook.

Activity

  1. ritch commented on Sep 4, 2014

    @ritch
    MemberAuthor

    Related: #410

  2. bajtos commented on Apr 7, 2016

    @bajtos
    Member

    @ritch the link in the issue description is no longer valid :( I can also see that some work has been already done on this matter, see #410 (comment). Is this proposal still relevant today?

  3. loay commented on Jan 24, 2017

    @loay
    Contributor

    @ritch @bajtos
    Is this issue still valid or shall we close the issue?
    Thanks.

  4. bajtos commented on Jan 25, 2017

    @bajtos
    Member

    Since the issue was opened more than two years ago and there was very little discussion since then, I am closing it. @ritch feel free to reopen if you think this is still valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions