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

__init__.py:1: Implement Page context class. #240

Closed
0pdd opened this issue Dec 31, 2018 · 3 comments
Closed

__init__.py:1: Implement Page context class. #240

0pdd opened this issue Dec 31, 2018 · 3 comments
Assignees
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 Context feature

Comments

@0pdd
Copy link
Collaborator

0pdd commented Dec 31, 2018

The puzzle 207-f1b71ce7 from #207 has to be resolved:

# @todo #207:60m Implement Page context class.

The puzzle was created by Artemiy on 31-Dec-18.

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 Dec 31, 2018
* Create PaginatedProducts, fix some roughness.

* Create todo for mocked Context

* Create todo for Page context class

* Self-review fixes

* Apply review fixes

* Apply review-fixes #2
@ArtemijRodionov ArtemijRodionov 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 Jan 3, 2019
@duker33 duker33 added the Context feature label Jan 5, 2019
@duker33 duker33 removed the take it any teammate can take this issue and start working with it label Feb 11, 2019
@duker33 duker33 self-assigned this Feb 11, 2019
duker33 added a commit that referenced this issue Feb 13, 2019
duker33 added a commit that referenced this issue Feb 13, 2019
duker33 added a commit that referenced this issue Feb 13, 2019
duker33 added a commit that referenced this issue Feb 13, 2019
duker33 added a commit that referenced this issue Feb 13, 2019
duker33 added a commit that referenced this issue Feb 13, 2019
duker33 added a commit that referenced this issue Feb 14, 2019
* #255  PDD task to fix bad settings entry

* #255  Move part of products context to the qs

* rf#255  Remove redundant tests

* #240  Fix CI
duker33 added a commit that referenced this issue Feb 14, 2019
duker33 added a commit that referenced this issue Feb 14, 2019
duker33 added a commit that referenced this issue Feb 14, 2019
duker33 added a commit that referenced this issue Feb 14, 2019
duker33 added a commit that referenced this issue Feb 14, 2019
* #240  Process DB templates with new page view class

* #240  Create page context. Move base contexts to page module side

* #240  Rename module `db_views` to `display`

* #240  Add test for attribute access

* #240  Merge fix

* #240  Merge fix #2
@0pdd
Copy link
Collaborator Author

0pdd commented Feb 14, 2019

@0pdd 3 puzzles #267, #268, #269 are still not solved.

0pdd referenced this issue Mar 15, 2019
* stb#447  Move Request class to the refarm side

* stb#450  Create ContextDict type at refarm side

* stb#444  Move catalog Page to refarm side

* #fix  Context recursive imports

* #fix  Context recursive imports

# Conflicts:
#	catalog/newcontext/__init__.py

* rf#260  Rename "newcontext" to "context"
@0pdd
Copy link
Collaborator Author

0pdd commented Mar 16, 2019

@0pdd 2 puzzles #268, #269 are still not solved; solved: #267.

@0pdd
Copy link
Collaborator Author

0pdd commented Apr 3, 2019

@0pdd the puzzle #269 is still not solved; solved: #267, #268.

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 Context feature
Projects
None yet
Development

No branches or pull requests

3 participants