Skip to content

Handle calculated/transformed properties such as password upon 'read/write` #3468

Closed

Description

@rashmihunt

As per @raymondfeng "In general, we need to have a better way to handle calculated/transformed properties such as password upon 'read/write`. I guess we should open an issue for the broader feature." Further details for this feature is in #251

Activity

  1. JameyG-Unit commented on Aug 8, 2017

    @JameyG-Unit

    Will this be included as a 3.x update or in LoopBack 4? (In particular with reference to issue #251). It's really made using LoopBack quite a big pain for our project development.

  2. bajtos commented on Aug 9, 2017

    @bajtos
    Member

    So far, LoopBack 4 is using existing loopback-datasource-juggler for the ORM/persistence part. If things stay this way, then the changes described in this issue may become available in both 3.x and 4.x. Having said that, I am not sure what are the plans for implementing this issue, I don't think it's on our near-term roadmap (@kjdelisle please correct me if I am wrong).

  3. stale commented on Oct 8, 2017

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  4. stale commented on Oct 22, 2017

    @stale

    This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions