We currently use an App on Android, and is has a realy cool feature, you can assign a default percentage to each user (default and per transaction), so for example we have a couple here so they have a default percentage of 200% as they share the same money (And like that we don't need to split every purchase between the two of them).

Having this feature could be really cool.

Adds a history page (Resolves #426 ), showing all changes to the database.

Implemented using SQLAlchemy-continuum. Per #426, users can opt-out using a new interface on the Settings page and must opt-in to have their IP addresses recorded.

Users visiting the history page after reducing their privacy settings are prompted to delete the previously recorded data:

This PR also includes a reasonably comprehensive set of tests to assure the privacy protections work as intended and that log entries are created for manual & api operations.

Hi folks,

8 years ago, I published the first version of ihatemoney.

I'm happy with what we have done with this project : it's still straight to the point, not doing a lot of fancy cool stuff nobody needs, it's just doing a set of simple tasks, and it's doing them well.

Since its inception, we've had 10 releases (current version is 4.1.3 at the time of writing), and contributions from 39 persons, according to the git log.

I recently changed my professional career (I'm a brewer now!), and I don't want to spend time on maintaining software projects anymore. Not that it's a pain to do, or anything like it, it's actually quite some fun, but I just don't want to take this even so small amount of time, these days.

So, while I have no problem shutting things down, it would be phenomenal to have a set of people to take this over. The amount of maintaining-work is small : a few pull requests here and there, some reviews and some releasing work, it honnestly doesn't take too much time.

I really hope people will step-up, but if it doesn't happen I will archive the project. I'll wait until the end of January 2020 to decide.

So, if you're interested, please, let me know!

Cheers, Alex

Hey here :)

seeing some open issues, like #344 or #352 i was fiddeling with another nav rework... i should probably though more about the first iteration...

Done :

• [x] enable new langs (NL)
• [x] language switcher is recognisable
• [x] make project name visible (and display the possibility to switch)
• [x] add some nice svg icon
• [x] make the project switcher available on homepage if already logged
• [X] Add link to mobile app and doc in footer
• [x] move dashboard link to footer...

Hi, and thanks for this project, it's great :-) I just discovered it and I'm opening a few issues here and there to propose feedback. Hope it's the right way to do things around here!

The icon used as a favicon is too small for my eyes, or maybe it depends on the colors used, but I find it almost useless, and even counter-productive!

There are plenty of existing icons provided with CC license by the Nount project. What about this one, for instance?

https://thenounproject.com/search/?q=money&i=1406358

I was thinking, what about starting making tagged releases (or even just tagging on github) ?

It's a bit of work, but it would :

• make the install process a bit easier
• simplify third-party packaging (I'm thinking about https://github.com/YunoHost-Apps/ihatemoney_ynh )
• force us to keep track of changes in a ChangeLog

What do you think ?

Hi,

@almet just to know what you would think about switching to a single-page-app framework like AngularJS, ReactJS… Goal is to get better experience for the user (#113 will help that also). The REST API would allow us to switch to this approach quite easily.

I'm not asking anyone to do it. I just would like to know, if I PR that kind of big change, would it be welcome or not ?

@almet ?

Upgrade to Bootstrap 4 (see #168 )

Included

To summarize :

• better factorization of templates
• fix moving elements (ex: try switching from project page to home page, things in sidebar are moving)
• improve readability
• fix misaligned elements
• make more use of BS grid system
• better screen readers/aria support

Still on my TODO before it could get mergeable.

• [x] the calendar for date selection is appearing under the bill adding modal
• [x] fix datepicker language loading race condition
• [x] fix datepicker arrow icons
• [x] Add a scrollbar if the content is too big for the modal (intead of overflowing)
• [x] (chrome browser only) When you click on "add a bill" and then close the modal window, everything in the background shift a little bit.
• [x] Weird color changing of the font color when clicking « Add bill » button
• [x] Hovering a member « Reactivate » button shifts everything towards right on the sidebar
• other items reviewers will find :-)

May come later in a separate PR

• responsive design (this PR only offers decent display for huge/medium display, not for small/tiny ones) @aavenel offered its help.
• rethink the navbar so that its contents is placed less weirdly (I tried to keep the previous philosophy, with minor adjustements).

Reviewers/testers are more than welcome :-) (poke @aavenel & others)

Currently, the latest release 4.1.3 is broken for new installs (#540).

The new 5.0.0 release (#570) might still take some time to happen (fix pending issues, wait for translators to pick up new strings, etc). In addition, it drops support for python 2 and python 3.5, so even in the long run some people may not be able to switch to 5.0.0 immediately.

Thus, I would like to propose a new "stable" 4.1.4 release, based on 4.1.3 instead of master, that fixes the following issues with 4.1.3 (checked items are already part of the WIP branch):

• [x] Fix failed installation because dependencies were not being pinned (#540, #545, #558)
• [X] Fix compatibility with werkzeug 1.0 (#488)
• [X] backend: Trim usernames to remove leading or trailing spaces. This avoids a situation where different names can be visually identical (#367)
• [X] backend: Fix API to forbid project creation when the ALLOW_PUBLIC_PROJECT_CREATION setting is set to false (#496)
• [X] backend: Fix crash when a localized email template is missing (#592)
• [X] backend: Fix language code parsing (#589)
• [x] backend: Improve error handling when sending emails (#595)
• [X] UI: Fix datepicker that was being displayed twice on some browsers (#221)
• [X] UI: Fix "Submit and add a new one" button that had no effect when adding a bill (#498)
• [X] UI: Prevent bill cancellation when cancelling autocomplete (#506)
• [X] UI: Fix responsive width of homepage on small screns (#549)
• [X] UI: Fix color of the "Add a member" button (#499)
• [X] UI: Fix missing HTML tag (#583)
• [X] UI: Fix a small typo in the french project-reminder email (#486)
• [X] UI: Fix typo on message displayed when adding a member (#575)
• [X] Add translations for German, Spanish, Norwegian, and Indonesian
• [x] Add translation for Russian
• [X] Update translations for all languages

Any other fix I may have missed?

What do you think on principle? @almet @JocelynDelalande @0livd @eMerzh @Natim @Glandos (I hope I didn't forget anybody)

Hey, now that there are muliple person involve,

i was wondering if now is not a good time to cut a release (beta or some pre- thing) or at least determin a good time to do that.

also, not sure what's the best channel to discuss this, github issues?

There is no link to a legal disclaimer. It would be different for each instance, but I think it is a legal obligation. It could also indicate who and where the data is held, the license (because Github is ugly), etc...

Bumps sphinx from 5.3.0 to 6.0.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Updates the requirements on flask-limiter to permit the latest version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

The correct answer didn't work, neither with uppercase nor lowercase for the first letter. I got the read banner, telling me to do the Captcha again. When I switched to the english site it accepted the answer and worked just fine. Problem occured in Firefox 107.0.1 on Mac.

Description

To tackle #137, I took some ideas from the discussion under the issue and made some design changes that are different from the previous PR that was done:

• Bill Types are added in the Bill model and forms to differentiate refund/reimbursement from expenses of the project. Currently, only three types of bills are hardcoded in as the present for all projects: Expense, Reimbursement, and Transfer. Expense is the normal spending, Reimbursement bill serves to settle the debt within the project, and Transfer is any bills between members that should not be tracked as an expense.
• Settle button is added to directly add a Reimbursement bill to clear out the debt associated with another participant with one click rather than going through another form for better UX.
• To maintain the Statistics page's functionality, Monthly Expense would only track expense type bills, and when participant A reimburses participant B, A's paid amount would increase and B's paid amount would decrease by the reimbursed amount to maintain the relationship between paid, expense, and balance. (balances = Paid - Spent)

Fixes #137

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [✓] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Most tests associated with the Bill model are modified to be compatible with the new bill type attribute. New tests and validations are added for bill type, the pay button on the settle page, and statistics calculations. All tests pass except the broken CI/CD in history_test.py

Test Configuration:

• Firmware version: Windows 10
• SDK: Python 3.8.10

Checklist:

• [✓] My code follows the style guidelines of this project
• [✓] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [✓] My changes generate no new warnings
• [✓] I have added tests that prove my fix is effective or that my feature works
• [✓] New and existing unit tests pass locally with my changes
• [✓] Any dependent changes have been merged and published in downstream modules

To-Do: Documentation changes, inline documentation (ideally will be done in the next few days) Allow custom types to be added and removed in the project setting Add more statistics page for different bill types

I have edited two files for this functionality. The first is manage.py which uses the Click module to issue commands. The second is in main_test.py for testing. Let me know if you have any concerts / questions. Thank you, James.

Added Click command to display the number of projects. Options exist to specify for projects within the bounds of the specified number of bills (inclusive) and/or less than x days old.