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

Importers overhaul #1228

Draft
wants to merge 7 commits into
base: dev
Choose a base branch
from
Draft

Importers overhaul #1228

wants to merge 7 commits into from

Conversation

BielStela
Copy link
Contributor

General description

Please write a description. If the PR is hard to understand, provide a quick explanation of the code.

Designs

Link to the related design prototypes (if applicable)

Testing instructions

Provide minimal instructions on how to test this PR.

  • Apart from the added feature / bug fix, check overall performance, styling...

Checklist before merging

  • Branch name / PR includes the related Jira ticket Id.
  • Tests to check core implementation / bug fix added.
  • All checks in Continuous Integration workflow pass.
  • Feature functionally tested by reviewer(s).
  • Code reviewed by reviewer(s).
  • Documentation updated (README, CHANGELOG...) (if required)

Materials and indicators importer.
- Removes the dependency of hardcoded csv files in the source code
- Adds schemas for such jsons
- Allows different material and indicator sources
Copy link

vercel bot commented Feb 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
landgriffon-client ⬜️ Ignored (Inspect) Visit Preview Feb 19, 2025 9:14am
landgriffon-cookie-traceability ⬜️ Ignored (Inspect) Visit Preview Feb 19, 2025 9:14am
landgriffon-marketing ⬜️ Ignored (Inspect) Visit Preview Feb 19, 2025 9:14am

@BielStela BielStela marked this pull request as draft February 17, 2025 09:42
indicator_coefficient_config: str


settings = Settings()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removing this would break the current set up, can we leave it for now? (In case we aim to have this PoC merged until we can fully switch to a new, shiny, performant, amazing data-importing approach?

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