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

refactor: move all requires-* to common folder #2842

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

Borda
Copy link

@Borda Borda commented Apr 30, 2024

This is just a suggestion, and fell free to reject it fro any reason, but I believe this would make the project navigation easier as all requirements files will we grouped in a single folder and not pealing in the root 🦩

Contributor Checklist

  • I have broken down my PR scope into the following TODO tasks
    • task 1
    • task 2
  • I have run the tests locally and they passed. (refer to testing section in contributing)
  • I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR

optionals

  • I have added entry in the CHANGELOG.md
  • If this PR needs a follow-up in dash docs, community thread, I have mentioned the relevant URLS as follows
    • this GitHub #PR number updates the dash docs
    • here is the show and tell thread in Plotly Dash community

@T4rk1n
Copy link
Contributor

T4rk1n commented May 28, 2024

Sorry it took a long time to review, I couldn't decide if I like this change or not.

On one hand I like to have them easily accessible at the root for ease of use and that way our dependencies are right on the github front page for everyone to see.

But putting them in a subfolder is actually a bit better for completion on the shell and the root is kinda crowded making the requirements files requires scrolling to get to them.

I would just rename the requires folder to requirements to be more like the standard requirements.txt of Python projects then I think we are good with this change.

cc @ndrezn @gvwilson

@gvwilson
Copy link

thanks @T4rk1n - @Borda, are you OK making the suggested change and pushing again?

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

3 participants