Implement BuyInAmount Selector Component (Issue #3) #15
@ -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;
|
||||
|
125
components/BuyInSelector.tsx
Normal file
@ -0,0 +1,125 @@
|
||||
|
||||
import React, { useState } from "react";
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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";
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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";
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>>;
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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];
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 }) => {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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("");
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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) => {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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) {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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("");
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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) => {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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("");
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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);
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 (
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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" />
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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) => (
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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={[
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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)}
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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"
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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"
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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}>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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"}
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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>
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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({
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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: {
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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,
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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",
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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 have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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;
|
||||
![]() I have a couple concerns with hardcoding this reference here.
One approach would be to save and render the image locally in our app. This solves point 1 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
![]() 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.
![]() I've replaced the external image link with the MaterialIcons from @expo/vector-icons, which addresses both the dependency issue and the rights concern. 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.
|
88
components/__tests__/BuyInSelector.test.tsx
Normal 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);
|
||||
});
|
||||
});
|
I have a couple concerns with hardcoding this reference here.
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.
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
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.
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.