Version 1.1.0

[ssestak]

• Template Updates
  • Removed SwiftLint warnings
  • Omitted application prefix in naming
  • Dropped class prefix in mock view model events
• Added commentary explaining anti-pattern of adding view modifiers in coordinator root view
• Alerts no longer managed by coordinators; their presentation is now individual view's responsibility
• Scene Delegate
  • Introduced view modifier in helpers
• Destination IDs
  • Integrated @EnumIdentifiersGenerator macro for auto-generating code for Hashable and Identifiable protocol conformance
  • The macro produces nested enum for ID generation for enum cases
• Introduced FlowProvider in helpers
• For coordinators, integrated ModalCoverModel<Destination> to avoid UI confusion regarding sheet and full screen cover presentation order

Prerequisites for Merging:

• New projects must specify a key-value pair for LaunchScreen in Info.plist to ensure proper display
• Macro
  • Requires importing EnumIdentifiersGenerator currently, but ideally, it should be part of FuturedArchitecture
    • UPDATE: Macro moved into a separate git repository
  • It doesn't account for situation when Destination ID needs to be computed using an associated value
    • UPDATE: DONE

Macro Expansion Example:

[mikolasstuchlik]

Overall a great piece of pioneering work!

[mikolasstuchlik]

Suggested change

	# Example #
	# Example #
	Declare a `protocol` conforming to the composition. The protocol should only be conformed to by enums. We use the requirements to force appearance of certain cases: [SE-0280](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0280-enum-cases-as-protocol-witnesses.md).

[mikolasstuchlik]

We probably should use naming which does not appear to have a special meaning, if it is only an example.

Suggested change

	static var destination: Self { get }
	static var end: Self { get }
	static var someDestination: Self { get }
	static var otherDestionation: Self { get }

[mikolasstuchlik]

What is a reusable scene flow provider? Is my suggestion correct?

Suggested change

	A protocol providing an interface for reusable scene flow providers.
	A protocol providing an interface for reusable scene flow providers. *Reusable scene flow provider* is part of a scene flow, which can be used as a part of more *Flow Coordinators*. The shared section of the flow is taken out of the *Flow Coordinator* and placed into a class conforming to `CoordinatorSceneFlowProvider`.

[mikolasstuchlik]

I still think we should make the @EnumIdentable add the conformance. I don't think it's MUST-HAVE at this point, but please, file an Issue to this effect.

[mikolasstuchlik]

Suggested change

[mikolasstuchlik]

I don't see why we need to do this. The Destination should be only a generic parameter of the ___VARIABLE_sceneFlowProviderIdentifier___SceneFlowProvider and conformed to by the Destinations of the Flow cooridnators.

If I am not correct, why do we need ___VARIABLE_sceneFlowProviderIdentifier___FlowDestination at all?

[mikolasstuchlik]

It is still not fully clear to me, how the Scene Provider should work. I don't want to hinder the acceptance because of the documentation. I have made some requests and the rest of it can be deferred to an Issue (on both FuturedKit and macros).

However, I'm reluctant to merge Scene Provider in this state.

[mikolasstuchlik]