Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

models.py:156-157: Remove Series.slug field. Series... #705

Open
0pdd opened this issue Jun 26, 2019 · 1 comment
Open

models.py:156-157: Remove Series.slug field. Series... #705

0pdd opened this issue Jun 26, 2019 · 1 comment
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it

Comments

@0pdd
Copy link
Collaborator

0pdd commented Jun 26, 2019

The puzzle 669-7e706acd from #669 has to be resolved:

stroyprombeton/stroyprombeton/models.py

Lines 156 to 157 in dde6256

# @todo #669:60m Remove `Series.slug` field.
# Series page already contains it.

The puzzle was created by duker33 on 26-Jun-19.

Estimate: 60 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.
@0pdd
Copy link
Collaborator Author

0pdd commented Jun 26, 2019

@artemiyds2 @duker33 please pay attention to this new issue.

0pdd referenced this issue Jun 26, 2019
@duker33
#669 Create sections (#700)
dde6256 
* #558  Rm redundant pdd subtask

* #669  Draft for a  Section model code

* #669  Handle code duplication with PDD subtask

* #669  Create sections migrations

* #584  Rm closed manually pdd subtask

* #669  Create section page with test

* #669  Apply linter rules

* #669  Create subtasks for section feature

* #699  Apply linter rules

* #699  Review#1 fixes. Section: get_min_price, rm slug, tests subtask

* #699  Review#1 fixes. Rm search, fix tests setUp, subtask seo_texts exploring
@0pdd 0pdd mentioned this issue Jun 26, 2019
Merged
@duker33 duker33 added 1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it labels Jun 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@duker33 @0pdd