Implement BuyInAmount Selector Component (Issue #3) #15

Merged
Vutukuri15 merged 2 commits from vutukuri15/3 into main 2025-02-09 21:37:45 -08:00
3 changed files with 231 additions and 1 deletions

View File

@ -1,9 +1,17 @@
import React, { useState } from "react";
import { ScrollView, Text } from "react-native";
import { ScrollView, Text, Alert, Button } from "react-native";
import PlayerSelector from "@/components/PlayerSelector";
import BuyInSelector from "@/components/BuyInSelector";
const IndexScreen = () => {
const [playerCount, setPlayerCount] = useState(2);
const [buyInAmount, setBuyInAmount] = useState<number | null>(null);
const handleSave = () => {
if (buyInAmount === null) {
Alert.alert("Error", "Please select a valid buy-in amount");
}
};
return (
<ScrollView contentContainerStyle={{ padding: 20, flexGrow: 1 }}>
@ -15,7 +23,16 @@ const IndexScreen = () => {
playerCount={playerCount}
setPlayerCount={setPlayerCount}
/>
<BuyInSelector setBuyInAmount={setBuyInAmount} />
<Button
title="Save"
onPress={handleSave}
disabled={buyInAmount === null}
/>
</ScrollView>
);
};
export default IndexScreen;

View File

@ -0,0 +1,125 @@
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
import React, { useState } from "react";
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
import {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
View,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
Text,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
TextInput,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
TouchableOpacity,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
StyleSheet,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
} from "react-native";
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
import { MaterialIcons } from "@expo/vector-icons";
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
interface BuyInSelectorProps {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmount: React.Dispatch<React.SetStateAction<number | null>>;
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const defaultBuyInOptions = [10, 25, 50];
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const BuyInSelector: React.FC<BuyInSelectorProps> = ({ setBuyInAmount }) => {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const [customAmount, setCustomAmount] = useState("");
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const [buyInAmount, setBuyInAmountState] = useState<number | null>(null);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const handleCustomAmountChange = (value: string) => {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const numericValue = parseFloat(value);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
if (!isNaN(numericValue) && numericValue >= 0) {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setCustomAmount(value);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmountState(numericValue);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmount(numericValue);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
} else {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setCustomAmount("");
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmountState(null);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmount(null);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
};
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const handleBuyInSelection = (amount: number) => {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmountState(amount);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setCustomAmount("");
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
setBuyInAmount(amount);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
};
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
return (
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<View style={styles.container}>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<View style={styles.header}>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<MaterialIcons name="monetization-on" size={30} color="green" />
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<Text style={styles.title}>Select Buy-in Amount:</Text>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
</View>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<View style={styles.optionsContainer}>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
{defaultBuyInOptions.map((amount) => (
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<TouchableOpacity
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
key={amount}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
style={[
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
styles.buyInButton,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
buyInAmount === amount ? styles.selectedButton : null,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
]}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
onPress={() => handleBuyInSelection(amount)}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<Text style={styles.buttonText}>{amount}</Text>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
</TouchableOpacity>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
))}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
</View>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<Text style={styles.orText}>Or enter a custom amount:</Text>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<TextInput
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
style={styles.input}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
value={customAmount}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
onChangeText={handleCustomAmountChange}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
placeholder="Enter custom buy-in"
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
keyboardType="numeric"
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
/>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
<Text style={styles.selectionText}>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
Selected Buy-in: {buyInAmount !== null ? buyInAmount : "None"}
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
</Text>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
</View>
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
);
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
};
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
const styles = StyleSheet.create({
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
container: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
padding: 20,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
header: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
flexDirection: "row",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
alignItems: "center",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
marginBottom: 10,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
title: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
fontSize: 22,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
marginLeft: 10,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
optionsContainer: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
flexDirection: "row",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
justifyContent: "space-around",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
marginVertical: 10,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
buyInButton: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
backgroundColor: "#ddd",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
padding: 10,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
borderRadius: 5,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
selectedButton: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
backgroundColor: "#4caf50",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
buttonText: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
fontSize: 16,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
orText: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
marginTop: 10,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
textAlign: "center",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
input: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
borderWidth: 1,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
borderColor: "#ccc",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
padding: 8,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
marginVertical: 10,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
borderRadius: 5,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
selectionText: {
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
marginTop: 15,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
fontSize: 16,
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
fontWeight: "bold",
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
},
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
});
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.
export default BuyInSelector;
djwesty commented 2025-02-09 19:35:52 -08:00 (Migrated from github.com)
Review

I have a couple concerns with hardcoding this reference here.

  • The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience
  • Though you may know its ok, I'm not sure if we have the rights to use this for our app.

One approach would be to save and render the image locally in our app. This solves point 1
Another approach would be to use some public icons, like @expo/vector-icons. If there is a good match, that addresses point 1 and 2.

This should be fixed, but up to you on your approach. You can resolve this thread when done

I have a couple concerns with hardcoding this reference here. * The link is a dependency of our app. If it breaks one day or the user has no network, could be a bad experience * Though you may know its ok, I'm not sure if we have the rights to use this for our app. One approach would be to save and render the image locally in our app. This solves point 1 Another approach would be to use some public icons, like [@expo/vector-icons](https://icons.expo.fyi/Index). If there is a good match, that addresses point 1 and 2. This should be fixed, but up to you on your approach. You can resolve this thread when done
Vutukuri15 commented 2025-02-09 20:11:27 -08:00 (Migrated from github.com)
Review

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.

Thanks for the feedback! I'll check local storage or @expo/vector-icons and update once fixed.
Vutukuri15 commented 2025-02-09 21:28:07 -08:00 (Migrated from github.com)
Review

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern.
Let me know if there's anything else to modify.

I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. Let me know if there's anything else to modify.

View File

@ -0,0 +1,88 @@
import React from "react";
import { fireEvent, render } from "@testing-library/react-native";
import BuyInSelector from "@/components/BuyInSelector";
jest.mock("@expo/vector-icons", () => {
const React = require("react");
const { Text } = require("react-native");
return {
MaterialIcons: () => <Text>MaterialIcons</Text>,
};
});
describe("BuyInSelector Component", () => {
it("renders the buy-in options and input correctly", () => {
const setBuyInAmount = jest.fn();
const { getByText, getByPlaceholderText } = render(
<BuyInSelector setBuyInAmount={setBuyInAmount} />
);
expect(getByText("Select Buy-in Amount:")).toBeTruthy();
expect(getByText("10")).toBeTruthy();
expect(getByText("25")).toBeTruthy();
expect(getByText("50")).toBeTruthy();
expect(getByPlaceholderText("Enter custom buy-in")).toBeTruthy();
});
it("sets a predefined buy-in amount correctly", () => {
const setBuyInAmount = jest.fn();
const { getByText } = render(
<BuyInSelector setBuyInAmount={setBuyInAmount} />
);
fireEvent.press(getByText("25"));
expect(setBuyInAmount).toHaveBeenCalledWith(25);
});
it("sets a custom buy-in amount correctly", () => {
const setBuyInAmount = jest.fn();
const { getByPlaceholderText } = render(
<BuyInSelector setBuyInAmount={setBuyInAmount} />
);
fireEvent.changeText(getByPlaceholderText("Enter custom buy-in"), "100");
expect(setBuyInAmount).toHaveBeenCalledWith(100);
});
it("resets custom amount if invalid input is entered", () => {
const setBuyInAmount = jest.fn();
const { getByPlaceholderText } = render(
<BuyInSelector setBuyInAmount={setBuyInAmount} />
);
fireEvent.changeText(getByPlaceholderText("Enter custom buy-in"), "-10");
expect(setBuyInAmount).toHaveBeenCalledWith(null);
});
it("clears the custom amount when selecting a predefined option", () => {
const setBuyInAmount = jest.fn();
const { getByText, getByPlaceholderText } = render(
<BuyInSelector setBuyInAmount={setBuyInAmount} />
);
fireEvent.changeText(getByPlaceholderText("Enter custom buy-in"), "100");
fireEvent.press(getByText("50"));
expect(setBuyInAmount).toHaveBeenCalledWith(50);
});
it("handles valid and invalid input for custom amount correctly", () => {
const setBuyInAmount = jest.fn();
const { getByPlaceholderText } = render(
<BuyInSelector setBuyInAmount={setBuyInAmount} />
);
fireEvent.changeText(getByPlaceholderText("Enter custom buy-in"), "75");
expect(setBuyInAmount).toHaveBeenCalledWith(75);
fireEvent.changeText(getByPlaceholderText("Enter custom buy-in"), "-5");
expect(setBuyInAmount).toHaveBeenCalledWith(null);
fireEvent.changeText(getByPlaceholderText("Enter custom buy-in"), "abc");
expect(setBuyInAmount).toHaveBeenCalledWith(null);
});
});