<commit_before>package metadata


/**
 * Represents a single issue
 * 
 */
case class Issue(code: String, message: String, why:String, howToFix: String){ }

object Issues {

    val all = List(
Issue(
"RS001",
"We've detected that your using a legacy call that's been deprecated. At one point it was possible to use only `account_id` but now `payment_provider_id` is a required field. If your users don't have a `payment_provider_id`, then still include the field, just set it to null.",
"""
You're probably only going to run into this issue if you've been using Referral SaaSquacth for a long time and you are one of our first users.

If you just recently started using Referral SaaSquatch, then you've probably worked yourself into a strange state and should get in touch with us to see how you got here.

If you're one of our existing customers, then you might be mid migration between the old world when `account_id` was the only required variable to the new world where `payment_provider_id` is now always required. 
This error is probably happening because `payment_provider_id` hasn't been included in all of your squatch.js init calls or links to the mobile web view.
""",
"""
 - Make sure you're using a valid `payment_provider_id`
"""),
Issue(
"RS002",
"For security reasons, you must include a `checksum` when `payment_provider_id` is set to null.",
"""
When you're using third party javascript like Squatch.js it's possible for your customers to arbitrarily change the data that you've passed into Squatch.js. For example, a clever user could potentially abuse
your system by setting `account_status: "PAID"`. To prevent this, we require a `checksum` as a security measure whenever a `payment_provider_id` doesn't exist.

We recommend that all our customers use a `checksum` to enable [Signed Requests](/squatchjs/signed-requests). It's a good thing to use.
""",
"""
 - Read the article about [Signed Requests](/squatchjs/signed-requests)
 - Make sure to include a `checksum`<commit_msg>LV: Added comments to link to Drive spreadsheet<commit_after>package metadata


/**
 * Represents a single issue
 * 
 */
case class Issue(code: String, message: String, why:String, howToFix: String){ }

/**
 * List of all issues codes
 * 
 * Original list of codes: https://docs.google.com/a/referralsaasquatch.com/spreadsheets/d/1R5gqU5EVfbGShopzIVsu4rRoKn3uWknBA2FsGl3uufw/edit#gid=0
 */
object Issues {

    val all = List(
Issue(
"RS001",
"We've detected that your using a legacy call that's been deprecated. At one point it was possible to use only `account_id` but now `payment_provider_id` is a required field. If your users don't have a `payment_provider_id`, then still include the field, just set it to null.",
"""
You're probably only going to run into this issue if you've been using Referral SaaSquacth for a long time and you are one of our first users.

If you just recently started using Referral SaaSquatch, then you've probably worked yourself into a strange state and should get in touch with us to see how you got here.

If you're one of our existing customers, then you might be mid migration between the old world when `account_id` was the only required variable to the new world where `payment_provider_id` is now always required. 
This error is probably happening because `payment_provider_id` hasn't been included in all of your squatch.js init calls or links to the mobile web view.
""",
"""
 - Make sure you're using a valid `payment_provider_id`
"""),
Issue(
"RS002",
"For security reasons, you must include a `checksum` when `payment_provider_id` is set to null.",
"""
When you're using third party javascript like Squatch.js it's possible for your customers to arbitrarily change the data that you've passed into Squatch.js. For example, a clever user could potentially abuse
your system by setting `account_status: "PAID"`. To prevent this, we require a `checksum` as a security measure whenever a `payment_provider_id` doesn't exist.

We recommend that all our customers use a `checksum` to enable [Signed Requests](/squatchjs/signed-requests). It's a good thing to use.
""",
"""
 - Read the article about [Signed Requests](/squatchjs/signed-requests)
 - Make sure to include a `checksum`
{'fraction_non_alphanumeric': 0.07584735719364778, 'fraction_numerical': 0.004740459824602986, 'mean_word_length': 4.6796769851951545, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1971144', 'n_tokens_mistral': 1215, 'n_tokens_neox': 1137, 'n_words': 594}