-
Notifications
You must be signed in to change notification settings - Fork 23
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
Include old messages in a chain when replying #3
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.5 ETH (82.14 USD @ $164.27/ETH) attached to it as part of the ArweaveTeam fund.
|
Bitcoin bounty page: https://gitcoin.co/issue/ArweaveTeam/weavemail/3/2800 |
Am starting work on this one now. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 12 months from now. 1) iamonuwa has been approved to start work. Declaring interest in getting this done now. ETA 3 hours Learn more on the Gitcoin Issue Details page. |
@iamonuwa Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
hi i can provide a PR |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 11 months from now. 1) codi45 has been approved to start work. add field for previous Message in permamail, Learn more on the Gitcoin Issue Details page. |
PR get merged with the previous one for UNIXTIMESTAMP |
Was addressed in #7. |
Hi @ldmberman could you please valid my applied for work on gitcoin so i could submit thanks |
Done @codi45 ! |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 0.5 ETH (86.79 USD @ $173.58/ETH) has been submitted by: @samcamwilliams please take a look at the submitted work:
|
Hi @ldmberman how would you like to style the subject line. |
@codi45 I think it makes sense to style them similarly to how "Mail recipient" and "Mail content" are styled on the "Write a new permamail" page. |
Hi @samcamwilliams I think you forgot to valid this bounty thanks |
Thanks, @codi45 ! Validating it now. @ldmberman and I are also starting a DAO to govern the development of weavemail. We will use it to vote on merging PRs etc., if there is every contention. We would like to give you some tokens for contributing. Do you have an Ethereum metamask wallet we can send some governance tokens to? |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 0.5 ETH (104.03 USD @ $208.07/ETH) attached to this issue has been approved & issued to @codi45.
|
Hi @samcamwilliams yes sure, Thanks 0x2f08F8112325639F2FB86A5841eE16D905FAf718 |
When pressing the 'reply' button on the message view page we should include the contents of the previous message in the compose pain as so:
This should be a fairly simple change around here.
We should also increase the default vertical size of the compose pain in order to accommodate the increased amount of text it will typically show.
The text was updated successfully, but these errors were encountered: