Changes between Version 1 and Version 2 of Ticket #18296, comment 6


Ignore:
Timestamp:
06/19/2012 10:18:39 PM (3 years ago)
Author:
SmileyChris
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18296, comment 6

    v1 v2  
    11Talking with Vanessa, we teased out the backwards incompatibilities of always creating the app folder.
    22
    3 One solution is to only create the app folder if the target folder name differs. This means that we keep backwards compatibility, but at the cost of less consistent behaviour.
     3One may assume the command should always create the app folder (i.e. move the contents of `django/conf/template` to `django/conf/template/app_name`). Unfortunately, it's not that easy - because then without a target, you'd end up with `app_name/app_name`
    44
    5 The other one is that we just assume the command should always create the app folder. The easiest way to do this would be to move the contents of `django/conf/template` to `django/conf/template/app_name`. This would change the format from that implemented by any existing third-party app templates, but that's not the end of the world.
     5One solution is to only create the app folder if the target folder's basename differs from the app name. This means that we keep backwards compatibility, but at the cost of less consistent behaviour.
    66
    7 I'm leaning towards simply moving the templates inside `app_name`.
     7The more consistent way would be to always create the app_name subdirectory when dealing with an explicit target. Again though, this changes the contract from the current behaviour.
Back to Top