vergegroup / swift-verge Goto Github PK

#220

I am using SwiftUI combine State effect by StoreReader {}.
But there is an error warning and the UI freezes, I don't know what to do?

xCode: Version 15.0 (15A240d)
IPhone RealDevice: iPhone 11 - iOS 16.5.1

The Changes contains new value and old value to get the boolean value that indicates if the property has been updated.
If the value struct is a large structure, deallocation will take many CPU usages.

• 🔸Delete Getter #106 by @muukii
• 🔸Make Changes Class #105 by @muukii
• 🔸Introduce assignment operator #104 by @muukii
• 🔸Add changed method for changes stream #103 by @muukii
• 🔸Revert "Make it commit order and receive order are same in concurrent" #102 by @muukii
• 🔸Make it commit order and receive order are same in concurrent #101 by @muukii
• 🔸Muukii/remove dispatch #100 by @muukii
• 🔸Cleanup #99 by @muukii
• 🔸Derived ORM Operators #98 by @muukii
• 🔸State slicing #97 by @muukii
• 🔸To avoid dangling pointer or memory leaks #96 by @muukii
• 🔸[VergeClassic] rename emit to send #95 by @muukii
• 🔸Fix Getter RxGetter #94 by @muukii
• 🔸Remove EqualityComputer #93 by @muukii
• 🔸Update StoreWrapperType #92 by @muukii
• 🔸StoreWrapperType #91 by @muukii
• 🔸Introduce Changes #90 by @muukii
• 🔸Remove KeyPath selector for Swift5.2 #89 by @muukii
• 🔸Computed Property #88 by @muukii
• 🔸Remove ViewModelBase #87 by @muukii
• 🔸New API to make a Getter #86 by @muukii
• 🔸Remove KeyPath changed #85 by @muukii
• 🔸Remove replace() #83 by @muukii
• 🔸Use unfair-lock in EqualityComputer #84 by @muukii
• 🔸AnyEntity stop using ref inside #82 by @muukii
• 🔸Allow the instantation of NoState #81 by @Aymenworks
• 🔸Fix data-race in EqualityComputer #80 by @muukii
• 🔸Remove find method that returns set with Hashable #79 by @muukii
• 🔸Use encodable in logging #78 by @muukii
• 🔸Rename init label on Dispatcher #77 by @muukii
• 🔸Filter with Fragment #76 by @muukii
• 🔸Make ContextualDispatcher RefType to avoid retain self #75 by @muukii
• 🔸Make Fragment propertyWrapper #74 by @muukii
• 🔸Add method of making nonnull getter from id #73 by @muukii
• 🔸Add DebugLog to Comparer #72 by @muukii
• 🔸Update Storage + Rx #71 by @muukii
• 🔸Update subject management #70 by @muukii
• 🔸andFilter -> filter #69 by @muukii
• 🔸Create JSON to print log #68 by @muukii
• 🔸Add new init to Comparer #67 by @muukii
• 🔸Update implementation of Index #66 by @muukii
• 🔸Fix dispatch log #65 by @muukii
• 🔸Support Swift5.2 #64 by @muukii
• 🔸Enable library evolution #63 by @muukii
• 🔸Retain self when subscribing in Getter/RxGetter #61 by @muukii
• 🔸Update syntax of creating getter #60 by @muukii
• 🔸New Syntax to create Getter #59 by @muukii
• 🔸Use ref box to keep previous value #58 by @muukii
• 🔸[VergeRx] Add SubscriptionGroup #57 by @muukii
• 🔸Update ViewModel #56 by @muukii
• 🔸Remove mutation API from EntityTable #54 by @muukii
• 🔸Add ObservableObject to Getter #55 by @muukii
• 🔸Fix cast error #53 by @muukii
• 🔸Support Redirect tracking #52 by @muukii
• 🔸Breaking Changes #51 by @muukii
• 🔸Add StateScope #50 by @muukii
• 🔸TryMutation TryAction #49 by @muukii
• 🔸Revise API #48 by @muukii
• 🔸Merge VM and Store module #47 by @muukii
• 🔸Update Filter #46 by @muukii
• 🔸Add UpdatedMarker with FragmentState #45 by @muukii
• 🔸IdentifierType -> EntityIDRawType #44 by @muukii
• 🔸[Breaking change] New Getter #43 by @muukii
• 🔸VergeORM improve getter #42 by @muukii
• 🔸signpost #41 by @muukii
• 🔸EntityIdenetifier gets CustomStringConvertible #40 by @muukii
• 🔸Add map method to Storage and Getter #39 by @muukii
• 🔸Improve Entity Getter #38 by @muukii
• 🔸Improve Getter #37 by @muukii
• 🔸Rename #36 by @muukii
• 🔸AnyEntity #35 by @muukii
• 🔸Add updateExists #34 by @muukii
• 🔸Fix updateIfExists #33 by @muukii
• 🔸Add commitInline to Context #32 by @muukii
• 🔸Cache creating getter on ORM #31 by @muukii
• 🔸Update VergeORM + Getter #30 by @muukii
• 🔸Rename accept to commit/dispatch #29 by @muukii
• 🔸Change static to instance scopedKeyPath #28 by @muukii
• 🔸Allows creating custom Action/Mutation #27 by @muukii
• 🔸Getter #26 by @muukii
• 🔸InsertionResult #25 by @muukii
• 🔸Add Tests #24 by @muukii
• 🔸Modify BatchUpdatesContext #23 by @muukii
• 🔸Update #22 by @muukii
• 🔸HashIndex #20 by @muukii
• 🔸VergeORM Index #19 by @muukii
• 🔸Update ORM #18 by @muukii
• 🔸Brush up #17 by @muukii
• 🔸Update ViewModel #16 by @muukii
• 🔸Namespace Action Mutation #15 by @muukii
• 🔸Store #14 by @muukii
• 🔸Simplify Storage #13 by @muukii

Even if empty function does nothin, hashChanges is true. Why is that? I made the derived pipeline type memoized, still it has no effects. I also set counter the same value, hasChanges again true.

I did not understan why we need Verge Orm? Which case should we add to our project? Can you give some use cases for understanding? I think, in Verge we really do not normalizaton stuff like in Mobx. Am ı wrong?

Hi again,
I explored all the source code of the Verge. I understood that commit function is atomic operation. I thought it was kind of database transaction thing. My question is if any error throws in commit function ,the commit function rollback to old state? Because in db, this kind of thing it's successfuly made or failed.

Suggested by @JohnEstropia

Many times to create Derived from .chain
notifying and memorization also have a little bit of cost to perform.
if chaining condition is same, we can return shared derived.

I am using class as my state. However Verge says, you cannot use class type for state type. Can we make it?

Hi. Is it possible to combine two or more stores?

Hey there,

I'm trying to use Verge and VergeORM in my application. Right now I have a very small model with a couple entries and I'm trying to list all the entries using SwiftUI:

VStack {
    StoreReader(Pickup.shared.store) { state in
        VStack {
            ForEach(state.database.entities.home.allEntities()) { home in
                Text("\(home.rawID)")
            }
        }
    }
}

But on the StoreReader line, I get the following error:
Initializer 'init(debug:_:content:)' requires that 'EventEmitter<_StoreEvent<State, Never>>' conform to 'DispatcherType'

This seems to only happen if I add the ForEach block. Let me know if there's another way I should be doing this :~)

Version: 8.8.0

which is faster?

EventEmitter.subscribers

I see _read yield used in the code 。 Now I'm a little confused what does that mean

Can I make state history with Verge like in redux? For example Undo/redo feature?

You refer store object even though it's used only for dispatching action. Does it bring extra performance loss since any change in store will trigger view re-rendering? If yes, what is the good way to minimize this kind of loss?

struct MyView: View {

  let store: MyStore

  var body: some View {
    UseState(store) { state in
      Text(state.name)
      Button(action: {
        self.store.myAction()
      }) {
        Text("Action")
      }
    }
  }
}

Any chance there is gonna be support for carthage?

SwiftUI or UIKit based application.

Verge needs an app that represents how Verge works in state-management.
What's type of application is not specified.

Something like SNS would be good, like Spotify, Unsplash