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

[Lake][Validations] Lake validation and info logic should remain inside of lake module, not webapp module #1420

Open
idiom-bytes opened this issue Jul 18, 2024 · 0 comments
Labels
Type: Enhancement New feature or request

Comments

@idiom-bytes
Copy link
Member

Is your feature request related to a problem? Please describe.
Core lake module and CLI tool was moved outside of the module, and is no longer serving my own requirements. Rather, webapp/frontend modules should be using engine interfaces, not moving code around to serve it's own modules.
#1319 (comment)

Describe the solution you'd like
Keep core lake module and engine logic inside of /pdr_backend/lake/ module
/lake/ -> all core logic, objects, and interfaces
/lake_info/ -> whatever it needs to serve the data/results to the web app

core logic/components/APIs/cli inside of "core engine modules" should not be moved to the webapp/frontend modules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant