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

feat: add campaign application #643

Merged

Conversation

gparlakov
Copy link
Contributor

@gparlakov gparlakov commented Jun 15, 2024

  • start with adding the required tables in the db model
  • why separate object
    • the campaign application will contain sensitive and personal documents that should not be made public
    • the lifecycle of the CampaignApplication is dictated by a process of ensuring the potential campaign is transparent and legitimate

work on CampaignApplication

Motivation and context

  • start with adding the required tables in the db model
  • why separate object
    • the campaign application will contain sensitive and personal documents that should not be made public
    • the lifecycle of the CampaignApplication is dictated by a process of ensuring the potential campaign is transparent and legitimate

Testing

Steps to test

New endpoints

Environment

New environment variables:

  • NEW_ENV_VAR: env var details

New or updated dependencies:

Dependency name Previous version Updated version Details
dependency/name v1.0.0 v2.0.0

 - issue 1843 - start with adding the required tables in the db model
 - why separate object
    - the campaign application will contain sensitive and personal documents that should not be made public
    - the lifecycle of the CampaignApplication is dictated by a process of ensuring the potential campaign is transparent and legitimate
Copy link

github-actions bot commented Jun 15, 2024

✅ Tests will run for this PR. Once they succeed it can be merged.

schema.prisma Show resolved Hide resolved
schema.prisma Show resolved Hide resolved
schema.prisma Show resolved Hide resolved
@sashko9807 sashko9807 added the run tests Allows running the tests workflows for forked repos label Jun 17, 2024
@github-actions github-actions bot removed the run tests Allows running the tests workflows for forked repos label Jun 17, 2024
@sashko9807 sashko9807 merged commit 8a7bba1 into podkrepi-bg:master Jun 17, 2024
10 of 11 checks passed
gparlakov added a commit to gparlakov/podkrepi-bg-api that referenced this pull request Jun 21, 2024
- issue 1843 - start with adding the required tables in the db model
 - why separate object
    - the campaign application will contain sensitive and personal documents that should not be made public
    - the lifecycle of the CampaignApplication is dictated by a process of ensuring the potential campaign is transparent and legitimate
gparlakov added a commit to gparlakov/podkrepi-bg-api that referenced this pull request Jun 30, 2024
- issue 1843 - start with adding the required tables in the db model
 - why separate object
    - the campaign application will contain sensitive and personal documents that should not be made public
    - the lifecycle of the CampaignApplication is dictated by a process of ensuring the potential campaign is transparent and legitimate
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.

2 participants