fediversity/fediversity
13
2
Fork 6
Code Issues 124 Pull requests 22 Projects 1 Activity Actions

standardize casing conventions #496

New issue
Open
opened 2025-08-25 19:18:06 +02:00 by kiara · 0 comments
kiara commented 2025-08-25 19:18:06 +02:00
Owner
Copy link

As a developer,
I want to standardize coding case conventions,
so that we may reduce surprise for readers (and writers).

implementation notes

our codebase currently seems to contain names spanning:

  • camelCase
  • snake_case
  • kebab-case
  • lowercase

this poses questions on:

  • what to settle on, looking at existing conventions for any of our languages:
    • nix
    • python
    • bash
  • looking to enforce these by linters
    • nix: non-existent?
    • python
    • bash
**As** a developer, **I want** to standardize coding case conventions, **so that** we may reduce surprise for readers (and writers). ### implementation notes our codebase currently seems to contain names spanning: - camelCase - snake_case - kebab-case - lowercase this poses questions on: - what to settle on, looking at existing conventions for any of our languages: - [ ] nix - [ ] python - [ ] bash - looking to enforce these by linters - [ ] nix: non-existent? - [ ] python - [ ] bash
kiara added the
type: task
 label 2025-08-25 19:18:06 +02:00
kiara added a new dependency 2025-08-25 19:18:31 +02:00
#288 external developers empowered to contribute
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/pixelfed
pixelfed-ci
No results found.
Labels
Clear labels   
api service

features that may relate more to a (to be created) API service

  
blocked

   
bug

Anything that doesn't work as advertised

  
component: fediversity panel

   
component: nixops4

   
documentation

   
estimation high: >3d

   
estimation low: <2h

   
estimation mid: <8h

   
productisation

features out-scoped with the decoupling of the productisation effort

  
project-management

Project management related tasks

  
question

   
role: application developer

   
role: application operator

   
role: hosting provider

   
role: maintainer

   
security

   
technical debt

   
testing

   
type unclear

   
type: key result

   
type: objective

   
type: task

   
type: user story

   
user experience
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#288 external developers empowered to contribute}
fediversity/fediversity
Reference: fediversity/fediversity#496
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?