Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

models.py:48-50: Create fixtures for tags. Copy from SE... #166

Open
0pdd opened this issue Aug 25, 2018 · 2 comments
Open

models.py:48-50: Create fixtures for tags. Copy from SE... #166

0pdd opened this issue Aug 25, 2018 · 2 comments
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 Aug 25, 2018

The puzzle 162-13b68231 from #162 has to be resolved:

# @todo #162:60m Create fixtures for tags.
# Copy from SE all tags fixtures creation logic.
# Then move `shopelectro.tests.tests_models.TagModel` to this class.

The puzzle was created by duker33 on 25-Aug-18.

Estimate: 60 minutes,

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 referenced this issue Aug 25, 2018
* #162  Move Tags stuff from SE site to catalog module

* rf#162  Rebase fixes

* rf#162  Create pdd issue for tests moving

* #162  Review#1 minor fixes

* #162  Review#2 minor fix
@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 duplicate and removed 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 Aug 25, 2018
@duker33
Copy link
Collaborator

duker33 commented Aug 25, 2018

double of #165

@duker33
Copy link
Collaborator

duker33 commented Jun 10, 2019

#165 is closed as the duplicate. But seems the current task is original.
It's required for the system seems categories fixtures does not contain tags

@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 and removed duplicate labels Jun 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to 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
Projects
None yet
Development

No branches or pull requests

2 participants