disallow card names with handled file endings

open
,
low
,  
 

 

  • View
  • Changes
  • Options
  • Related
  • Edit
  • Offering/asking to add the card with the name. So trying to add 'blah.html' gets:

        Wagn doesn't allow file endings on card names. Shall we add this card as 'blah'?

    ...with the name field populated with 'blah', and any default content still filled out.

     

     

    Related support tickets: 
    Relevant user stories: 
     add one
  • View
  • Changes
  • Options
  • Related
  • Edit
  • Itching a bit at the idea of totally disallowing a card name. As the handled file endings expand, they will overlap with top level domains, and possibly other terms that people really will want to use for card names.

     

    How about changing it to offer to add the card with the stripped name as decribed above, but having a less prominent link to go ahead and add it with the full name they typed in? (And then when "foo.txt" is requested, giving "foo.txt" if it exists, otherwise looking for "foo".)

     

    disallow -> discourage?

     

    --John


    Also, note I added the tag "file types by ending" - anyone got a better term for our new nifty auto-handling of file types via their endings?

      --John Abbe.....Sun Jan 23 12:35:28 -0800 2011


    As long as we're doing this, we may as well disallow any endings that we're certain we're going to implement. See add file endings generating more file formats,

      --John Abbe.....Wed Feb 16 04:23:29 -0800 2011

     

    Notes

    add a note

    try it

     

    wagneers

    intro

    videos

    features

    syntax

    weekly calls

    ideas

     

    twitter

    mailing list

     

    developers

    roadmap

    next release

    tickets

    pack API

    REST API

    one-pager

     

    github

    mailing list

     

    wagn.org

    recent

    todo