Add basic donation records #18
Dismiss Review
Are you sure you want to dismiss this review?
Labels
Clear labels
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
integration
btcpay
integration
discourse
integration
ejabberd
integration
email
integration
ldap
integration
lndhub
integration
mastodon
integration
nostr
integration
remotestorage
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
No labels
kredits-2
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/akkounts#18
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This changeset adds the basic building blocks for account donation/payment tracking.
Admins can manually add and edit donation records for now. And Users can see their own donations on the (as-of-yet unlinked)
/donationspage.looks good to me.
not sure if we need all the scaffold API/jbuilder stuff for the Admin panel?
@@ -0,0 +4,4 @@# GET /donations# GET /donations.jsondef index@donations = current_user.donations.completedhmmm. we could show uncompleted for user to finish them. 🤔
but I guess showing only the completed ones keeps the page clean and shows the relevant information. - they can just start a new donation procss instead of finishing a not-completed one.
This is only a PR for the basic/manual donation records. Any payment-related questions have to be solved when integrating tracking for live donations.
@@ -3,6 +3,7 @@ class User < ApplicationRecord# Relationshas_many :invitations, dependent: :destroyhas_many :donationsmaybe add a
dependent: :nullify?Good hint!
@@ -0,0 +12,4 @@<% @donations.each do |donation| %><li><h3><%= donation.paid_at.strftime("%B %d, %Y") %>isn't that something like
l donation.paid_at, format: :short?I haven't done any localization or i18n anywhere in the app, but we should do that soon! We have a nice bonus of being able to deploy in multiple languages from the start.
Do we want to directly connect the akkounts app with the lightning node (to get new payment requests) or do you want to to have the BTCPay Server's invoice managment?
In the screenshot, the fiat amount has a "$" prefix and a "EUR" suffix.
The screenshot is outdated.
Good question. But not one for this PR. (I think using BTCPay for everything is easier, unless we want to track on-chain transactions with custom code.)
Thanks for the reviews!