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

chore: Repo cleanup and improve docs #2656

Merged
merged 3 commits into from
Dec 10, 2024
Merged

chore: Repo cleanup and improve docs #2656

merged 3 commits into from
Dec 10, 2024

Conversation

kimadactyl
Copy link
Member

@kimadactyl kimadactyl commented Dec 8, 2024

Completes easy spring cleaning jobs

Checklist:

  • I have performed a self-review of my own code,
  • I have commented my code, particularly in hard-to-understand areas,
  • I have made corresponding changes to the documentation,

Resolves #2636

Description

  • Make some comments more accurate
  • Remove empty folders
  • Remove unneeded PDFs

Motivation and Context

Cleaning up the repo to make it easier to navigate

Type of change

  • Code tidyup
  • Documentation update

How Has This Been Tested?

N/A

Huly®: PC-2663

@kimadactyl kimadactyl requested a review from lenikadali December 8, 2024 16:07
@kimadactyl kimadactyl self-assigned this Dec 8, 2024
@kimadactyl kimadactyl closed this Dec 9, 2024
@kimadactyl kimadactyl reopened this Dec 9, 2024
@kimadactyl
Copy link
Member Author

sorry huly sync doing weird things

│   │   ├── controllers
│   │   └── src
│   ├── jobs # Importer logic - jobs are created by cron (`/lib/tasks`). There's a readme here with more info
│   ├── mailers # Email configuration
│   ├── models
│   ├── policies # Pundit rules for who can do and access what
│   ├── uploaders # CarrierWave rules for handling image and logo uploads
│   ├── validators # Postcode validator - should possibly live somewhere else
│   ├── validators # Postcode validator - should possibly live somewhere else, or have other validators moved in here
Copy link
Collaborator

@lenikadali lenikadali Dec 9, 2024

Choose a reason for hiding this comment

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

comment: the only other place this kind of code would go (if just the postcode validator is in this folder) is in app/helpers

But this looks like a standard Rails app folder (meant to hold validation code that is used by models in app/models)

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm... as I understand it, code in app/concerns would be separate from app/validators. If there's more than enough overlap, I would merge the two (just did a skim; can take a closer look tomorrow with fresher eyes). Otherwise, they can be left as is.

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah i think can be left as is for sure its just a bit of a violation of single responsibility principle but theres no hurry to change it

@lenikadali
Copy link
Collaborator

Looks good to me ✨ Probably needs a check on staging to make sure we didn't break anything 😅

@kimadactyl
Copy link
Member Author

Looks good to me ✨ Probably needs a check on staging to make sure we didn't break anything 😅

if youre happy plz approve :) if you didnt know, main deploys to placecal-staging.org :)

@lenikadali
Copy link
Collaborator

Looks good to me ✨ Probably needs a check on staging to make sure we didn't break anything 😅

Plus this comment (non-blocking, was merely a response to the question 😇)

Copy link
Collaborator

@lenikadali lenikadali left a comment

Choose a reason for hiding this comment

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

LGTM

@kimadactyl kimadactyl merged commit e65dc23 into main Dec 10, 2024
2 checks passed
@kimadactyl kimadactyl deleted the repo-cleanup branch December 10, 2024 18:51
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.

Remove deprecated assets and folders
2 participants