-
Notifications
You must be signed in to change notification settings - Fork 7
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
Pass image instead of path and height #11
Conversation
sounds good to me, any other opinions @Orbion-J? |
Should we continue with this if @Orbion-J doesn't answer? |
hey, sorry I did not answer sooner. That's actually a better idea to give an image object I think, thank you for that. |
That's what I tried and gave me the error above. |
Here is an MWE: https://typst.app/project/rW8SSglf9kWEOikQNLIR3r |
Oh I see, that is a bit strange to me. Using a local import, I don't have such issue but with the |
Yes, I agree. If you are fine with it, let's just go with passing an |
Great! I'll create a release after taking a look at #14 |
Thanks! |
Thanks for the template! I wanted to try the recently added feature of adding an image (thanks @Orbion-J!), but struggled with including the image. It seems like typst searches for the image in the directory of moderner-cv, instead of the directory of the project, which uses moderner-cv. I get the following error:
Obviously, I don't want to put my image into this specific path, but rather in my project dir. Therefore, I propose to pass an
image
object instead of only the path. This also makes theimage-height
parameter obsolete as it is passed to theimage
function, which the user is now supposed to call.What do you think?