vakhokontridze / vcomponents Goto Github PK

When I use both versions, I get an error.

Hi,

Thank you for this amazing implementation of the components, learning so much from it.

I am just woundering if we have a Form with a number of textfields and the last one is a TextView field is there a solution to make sure where any TextField or TextView field scrolls up to be above the keyboard whenever the user starts to ente text?

Thanks.

Wael

Environment

• VComponents v4.0.4
• Xcode 14.3
• iOS 16.2

Description

I have a UIHostingViewController with a SwiftUI rootView, where the rootView calls .vAlert() and results in the following:

The vAlert and vToast don't respond to theme changes automatically they stay in light mode and won't change self
The colours are set in my Assets file

Example:

extension VAlertUIModel {
    
    public static var error: Self {
        var uiModel: Self = .init()
        
        uiModel.backgroundColor = Color("AlertBGColor", bundle: .none)
        uiModel.titleTextColor = Color("AlertTextColor", bundle: .none)
        uiModel.messageTextColor = Color("AlertTextColor", bundle: .none)
        
        return uiModel
    }
}

I have a VTextField with an onChange handler where the bound String variable is always one key stroke behind the actual string value. In UIKitTextFieldCoordinator.textFieldDidChange() there's code to commit the text change before the changeHandler is called. However, UIKitTextFieldRepresentable.commitText() is called asynchronously and is executed after the change handler is called.

This code is all running on the main thread so is there a reason to wrap the commitText string assignment in a DispatchQueue.main.async?

If it has to be assigned asynchronously, the changeHandler should be run as a completion handler in the async closure.

Keep getting this error after testing with the terminal

Command: xcodebuild -project test.xcodeproj -scheme test -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 15 pro,OS=17.2' test | xcbeautify