Git Product home page Git Product logo

Comments (7)

rkeithhill avatar rkeithhill commented on July 21, 2024 1

That's wasn't the intended usage but hey, if it works... :-)

from plaster.

rkeithhill avatar rkeithhill commented on July 21, 2024

That is a bad example for choice input. The better example is in Examples\NewModuleTemplate\plasterManifest.xml.

WRT to destination path, Invoke-Plaster will create the destination path if it doesn't exist. Ditto for file destination - if the parent folder(s) don't exist "within" the destination dir, they will be created.

What we are currently missing is a way to create an empty folder. Not that Git would allow you to commit that. #THINGSIDONTLIKEABOUTGIT :-)

from plaster.

gerane avatar gerane commented on July 21, 2024

I was able to create empty folders like this

<file source='Toolkit\Files\'
        destination='Toolkit\Files\'/>
<file source='Toolkit\SupportFiles\'
        destination='Toolkit\SupportFiles\'/>

from plaster.

gerane avatar gerane commented on July 21, 2024

lol

from plaster.

gerane avatar gerane commented on July 21, 2024

I take it back, it looks like it is not making the empty directories now. Is this eventually planned?

from plaster.

rkeithhill avatar rkeithhill commented on July 21, 2024

I updated the example in the DesignNotes.md document to reflect the current state of choice and multichoice functionality.

As for creating an empty directory, yes, I would like to support that. It should be easy enough to add. Just wondering though if a <directory destination="Toolkit\SupportFiles"/> directive would lead template authors to believe they have to do that for every subdir when <file .../> will create subdirs as long as their is a file go into them.

I wonder if it would be too weird if we supported this syntax:

<file source='' destination='Toolkit\Files\'/>

Oh wait a tic. That works (unintentionally) now! Is that sufficient long term?

from plaster.

gerane avatar gerane commented on July 21, 2024

I have been thinking this one over. I think this works as a short term solution if documented, but long term I feel this might be confusing. It would be ideal if someone can just quickly look at a manifest and understand how it works, and adding quirks like that kind of go against the way you would think directories should work.

I feel Plaster should try to stay as inviting and user friendly as possible. I am going to guess that a very large number of users who start using this have never used a generator like this before.

from plaster.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.