Skip to content

tree PUT bug #3

@abalmos

Description

@abalmos

put /bookmarks/services/target/jobs/
{ _id: 'resources/' }
2:30 PM what that does in oada/client is create a new resource and link it under
2:30 PM if you use the tree
2:30 PM i.e. the tree tells it that jobs/ should be a resource, and that resource doesn't exist
2:31 PM so it decides to make one, then put { _id: ... } to it which is basically a no-op
2:31 PM I believe we fixed this in oada-cache long ago, but new client hasn't had all the edge cases yet (edited)
2:31 PM so you can get around it by putting the jobkey in the body instead of just the link
2:31 PM but if you put to the jobkey in the url, tree put doesn't work

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions