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

Define "highlights" directly in view #31713

Merged
merged 2 commits into from Nov 7, 2019

Conversation

Hamms
Copy link
Contributor

@Hamms Hamms commented Nov 5, 2019

Description

Rather than defining a constant in the index view that's only ever used in the highlights view.

Reviewer Checklist:

  • Tests provide adequate coverage
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

Rather than defining a constant in the index view that's only ever _used_ in the highlights view.
@Hamms Hamms requested a review from breville November 5, 2019 22:47
@Hamms Hamms force-pushed the no-constant-assignment-in-templates branch from 4989f0e to de983ca Compare November 5, 2019 22:50
@Hamms Hamms merged commit 29cad9e into staging Nov 7, 2019
@Hamms Hamms deleted the no-constant-assignment-in-templates branch November 7, 2019 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants