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

how to maintain only part of the input path for the generated images in the image plugin? #67

Closed
nirjan-dev opened this issue Dec 22, 2020 · 0 comments · Fixed by #118
Closed

Comments

@nirjan-dev
Copy link

nirjan-dev commented Dec 22, 2020

My folders option for the image plugin looks like this

folders: [
        {
          src: '/assets/img/**/*',
          output: '/img',
        },
      ],

my folder structure in the assets directory looks like this

assets/img/blog/{blog-title}/{image-name}.png

right now using this config I'm getting an error that the destination path doesn't exist because it is looking for a path like this

/path-to-the-project/public/img/assets/img/blog/{blog-title}/{image-name}.png

I would like the generated path to be like this

/path-to-the-project/public/img/blog/{blog-title}/{image-name}.png

and if the directories are not there then it should create the directories, manually creating directories for the public folder wouldn't make much sense

Is there a fix for this?

noxasch added a commit to noxasch/plugins that referenced this issue Jun 16, 2021
- fix manifest not found when using **/*

close Elderjs#67
nickreese pushed a commit that referenced this issue Jul 30, 2021
* feat: add markdown content route config

- update index.spec.js

- reduce markdown input to bare minimum

address #61

* refactor: remove commented code

* docs: update plugin markdown docs

* feat: allow path/**/* usage for images src

- fix manifest not found when using **/*

close #67

* docs: update plugin-images docs

* fix(image-plugin): include plugin config

- resolves #119
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

Successfully merging a pull request may close this issue.

1 participant