Code change:
I think the description of the checkfunds method () is faulty. ! It should be: "A method that accepts an amount as an argument. It returns if the amount is greater than the balance of the budget category and returns otherwise. This method should be used by both the method and method." This is more logical, makes the code simpler and actually works with the tests. Browser Version: Firefox 79 on Ubuntu Linux Operating System: Ubuntu 20.04 LTS
this is genuinely a mistake as how can the amount which needs to be withdrawn be more than the balance in the ledger. amount can only be withdrawn if it is less than the balance in ledger. however there can be a probability that a part of that amount can be deducted from balance but the challenge stated nothing for the same. also the test module asked for a False return value which i think is wrong here in the challenge. !
Hello! Has any resolution to this been implemented? Im not entirely sure what to do about submitting this project because this error still exists. Any help is greatly appreciated!
I don't think so, hasn't changed. It doesn't matter though, design the project as if it was modified the way I suggested and it'll be fine.
Thank you, for opening this. For anyone reading, before a fix: Change this: To this in the file: Can I get a sanity check here? What needs to change on the fCC repl account? I am opening this up to first-timers only Here is the repo: The README description makes sense, but the tests do not, in my opinion. So, the README does not need to change.
Thanks for your patience and for catching this Also, thanks for @ mentioning me, Sorry I didn't see this sooner. My first thought is that we don't need to change the test, but just the README like suggested. It seems like is supposed to be used by the other methods to make sure that there's a sufficient balance before calling or . So in the current test: It makes sense that the first condition is false and the second is true -- you shouldn't be able to buy 10. It's just that the current instructions in the README doesn't reflect that. is that what you were thinking for the method? Also, to answer your question once we decide what to do here and fix things in the boilerplate repo, someone on the team can sign into and mirror those changes.
Thanks for that. I was thinking about the use of the method in an odd way.
I'm willing to work on this one if it's agreed that the README needs to be changed instead of the test.
Thanks, for your eagerness and patience. I was a bit quick with approving the change to be made. So, right now, I suggest you leave your current PR open as is. Once we come to a consensus here, we will be sure to let you know which changes (if any) to make on your PR.
no problem. I think it could work the other way around, we would just need to change the description a bit more and maybe change the method name to something like . I heard back from and he agrees that changing the README makes the most sense. The wording that suggested sounds good to me.
Just mirrored the changes from PR in the project: Thanks again everyone for your suggestions, reviews, and for this fix.

Related discussion:
text: <ins> { /* * ENVIRONMENTS * ================= */ // Define globals exposed by modern browsers. "browser": true, // Define globals exposed by jQuery. "jquery": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. "camelcase": true, // Prohibit use of == and != in favor of === and !==. "eqeqeq": true, // Suppress warnings about == null comparisons. "eqnull": true, // Enforce tab width of 2 spaces. "indent": 2, // Prohibit use of a variable before it is defined. "latedef": true, // Require capitalized names for constructor functions. "newcap": true, // Enforce use of single quotation marks for strings. "quotmark": "single", // Prohibit trailing whitespace. "trailing": true, // Prohibit use of explicitly undeclared variables. "undef": true, // Warn when variables are defined but never used. "unused": true, // Enforce line length to 80 characters "maxlen": 80, // Enforce placing 'use strict' at the top function scope "strict": true' } </ins>