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

relative versus absolute #9

Open
rngadam opened this issue Oct 22, 2013 · 1 comment
Open

relative versus absolute #9

rngadam opened this issue Oct 22, 2013 · 1 comment

Comments

@rngadam
Copy link
Contributor

rngadam commented Oct 22, 2013

I'm unclear as to why the absolute path is stored as the defaultUrl since the absolute path is already stored in path:

    "image": {
      "detail": {
        "depth": 8,
        "format": "JPEG",
        "oname": "IMG_0103.JPG",
        "mtime": "2013-10-11T16:53:30.000Z",
        "ctime": "2013-10-11T16:53:30.000Z",
        "size": 115351,
        "path": "/home/rngadam/letsface/src/prototype/public/images/detail/zbzkDZKIMM-detail.jpg",
        "defaultUrl": "/home/rngadam/letsface/src/prototype/public/images/detail/zbzkDZKIMM-detail.jpg",
        "dims": {
          "w": 400,
          "h": 300
        }
      },

Would it not be best to store the relative URL (minus the directory that has been configured for the plugin)? This would facilitate generation of URLs when retrieving images (in a REST interface for example).

It would also be best if a prefix could be provided when calling attach.

@ow
Copy link

ow commented Jul 19, 2014

I'm stuck on this too; not entirely sure how to retrieve it in an easy manner since it requires a full directory as opposed to a relative directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants