👔 for Business Logic

Hello @carloscuesta 😎!

• Emoji: 👔
• Code: :necktie:
• Description: Add or update business logic and utility functions.

This could sound like a catch-all, but I specifically discern a difference between architecture (the structure of your application), features (code being introduced that users will see), and business logic (stateful or utility logic in your application that does some sort of computation or calculation for internal application purposes).

An example of business logic unrelated to performance or bug fixing would be adding a way to track when all downloads are completed. I don’t mean this in the sense of analytics, but potentially for some other process in the future that another developer will use.

This is how you differentiate a feature (something exposed to the user) and business logic (something exposed to developers).

Another example would be a utility function. If you’re writing utility functions, that can happen in separate commits from other developers consuming those functions.

[seancrowe]

@Sawtaytoes I am going to make a pull request but I dropped “utility functions”. I think “utility functions” is a subset of business logic. So adding it seems odd, and then you will get people who want to add their own subsets of business logic. Like “Add or update business logic and utility functions and interfaces and… etc”. Better to just make it all under one label “business logic”.

See it looks so nice

[coyotte508]

Maybe this is something that is usually solved with scope?

✨ (back/api) Add new endpoint ✨ (back/utils) Add quick sort

From the scope we see if the module is intended for developers or not