Resolve step validations for imports
Reported by baphled (at boodah) | July 27th, 2010 @ 08:21 PM | in 0.8.2
Firstly we should refactor our feature create action.
From there we want to remove the unique validation on steps as well as decrease the feature character amount to 5.
Comments and changes to this ticket
-
baphled (at boodah) July 27th, 2010 @ 08:44 PM
- Milestone changed from “0.8.3” to “0.8.2”
- Milestone order changed from “14” to “0”
-
baphled (at boodah) July 28th, 2010 @ 07:13 PM
- Title changed from “Disable functionality to import a single feature” to “Resolve step validations for imports”
-
baphled (at boodah) July 28th, 2010 @ 08:20 PM
Moved feature import functionality to the sync action, created route and moved specs relating to the import functionality to the cover the new action. Next we'll work on the import based views and get them connected to our new action. Once this is complete we will remove the functionality from our create action
-
baphled (at boodah) July 28th, 2010 @ 10:15 PM
- State changed from “new” to “resolved”
Our forms are now connected to the new sync action and I have implemented specs to cover this.
I have also removed the import functionality from the features create action, as it is no longer needed.
As we are only uniqueness is only checked for on the create action we should be able to import without a problem.
This still leaves open the issue with steps not being unique but we'll deal with that later.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bridging the gap between clients and developers
baphled (at boodah)