Comments (11)
All good.
from treasury.
Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.
from treasury.
Treasury has the best documentation of the three projects. Vault's is okay, but it is also missing some key information. Reserve's Wiki is poor, but its javadocs are decent at least.
This doesnt seem to parse correctly
On the BankAccount section
Vault's bank accounts require an owner which is not suitable for all implementations. (...). Vault's require an owner.
Why say it twice?
That's all I could think of right now
from treasury.
Treasury has the best documentation of the three projects. Vault's is okay, but it is also missing some key information. Reserve's Wiki is poor, but its javadocs are decent at least.
This doesnt seem to parse correctly
On the BankAccount section
Vault's bank accounts require an owner which is not suitable for all implementations. (...). Vault's require an owner.
Why say it twice?
That's all I could think of right now
Thanks, will edit now.
from treasury.
Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.
Thanks for the clarification, I assumed it would be a long-term API. Reserve will not be referenced anywhere on Treasury's pages now. 👍🏻
from treasury.
I am satisfied with the state of the page so I will close this issue. Feel free to leave any more comments, I am just discarding it from our priorities.
from treasury.
There is a typo at the bank account section
reasury's bank accounts have none of these issues.
from treasury.
There is a typo at the bank account section
reasury's bank accounts have none of these issues.
Good catch! I also found I did not mention the bank permissions system. Fixed both 👍
from treasury.
Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.
Thanks for the clarification, I assumed it would be a long-term API. Reserve will not be referenced anywhere on Treasury's pages now. 👍🏻
While it does occasionally get updates, no it's not designed to be a long-term API currently.
from treasury.
Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.
Thanks for the clarification, I assumed it would be a long-term API. Reserve will not be referenced anywhere on Treasury's pages now. 👍🏻
While it does occasionally get updates, no it's not designed to be a long-term API currently.
Looks more like an API which is made for private use rather than an actual API. No bad feelings though.
from treasury.
It was never designed to be a long-lasting API and more of a stop-gap until something new came along.
🙂
from treasury.
Related Issues (20)
- Expanding #246
- General Javadoc Improvements
- `Response`: add method to fail with a given exception HOT 6
- `Account`: Change the return type of `retrievePermissionsMap` HOT 7
- Review API methods which do not return a Future+Response type. HOT 13
- `EconomyTransaction`: Rename some variables, getters and setters HOT 6
- `Currency`: Should we map display names against locales? HOT 3
- Responses vs Exceptions - differentiate and debate HOT 20
- `Account`: Rename `setPermission`, `hasPermission` to use a plural HOT 3
- Review methods which return TriStates but do not utilise all three possible states HOT 25
- `Account`: add another `setPermissions` method which accepts a `Map<perm, state>` HOT 2
- Change currency identifier to NamespacedKey HOT 6
- EconomyTransactionResult HOT 6
- Add abstract TreasuryException#getMessage(Locale) method
- Publish to Hangar HOT 5
- Last thoughts on Treasury v2's API? YOUR OPINION is wanted! HOT 10
- Write API Documentation in Wiki HOT 17
- Strip colours out of logging HOT 1
- Breaking Change Proposals ('Treasury v3')
- New Author HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from treasury.