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

TOK-475: add allocation context #374

Conversation

jurajpiar
Copy link
Contributor

@jurajpiar jurajpiar commented Nov 18, 2024

What

  • adds a context to handle allocations
  • adds a context to handle pagination
  • connects allocs context to allocs page

Task

@jurajpiar jurajpiar requested a review from a team November 18, 2024 13:24
@jurajpiar jurajpiar force-pushed the TOK-475/allocation_context branch 23 times, most recently from ef25b77 to b93df9e Compare November 21, 2024 00:37
@jurajpiar jurajpiar marked this pull request as ready for review November 21, 2024 01:22
@jurajpiar jurajpiar force-pushed the TOK-475/allocation_context branch 2 times, most recently from 53711fc to 47115cd Compare November 21, 2024 02:02
@antomor antomor changed the title feat(cr): add allocation context TOK-475: add allocation context Nov 21, 2024
@antomor antomor changed the base branch from develop to TOK-491/review-buildercontext November 21, 2024 15:15
@jurajpiar jurajpiar force-pushed the TOK-475/allocation_context branch from 3858645 to e618008 Compare November 21, 2024 15:15
@jurajpiar jurajpiar force-pushed the TOK-475/allocation_context branch from e618008 to e67463c Compare November 21, 2024 15:19
back to state

pagination and safer context return

chore: review allocations

fix: make builder context global
@jurajpiar jurajpiar force-pushed the TOK-475/allocation_context branch from e67463c to bb33c6c Compare November 21, 2024 15:20
@antomor antomor merged commit 5cc1729 into RootstockCollective:TOK-491/review-buildercontext Nov 21, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants