Are there any major blocking reasons the local dev...
# touchlab-tools
m
Are there any major blocking reasons the local dev flow is disabled when using a custom package file with KMMBridge? We wanted to be able to do local dev with a Package that has multiple targets so i threw together a dirty gradle task that basically copies what
SpmDependencyManager.modifyPackageFileVariables
does with the top variables block but changes the
url
and
checksum
bit to a
path
to the framework with the help of a second set of
//BEGIN
and
//END
comments. If there arent any crazy edge cases to consider i can probably make some time to open a PR
k
I don't know if there is a blocking reason. The practical reason is we've been less focused on publishing SPM and more focused on using KT source. KMMBridge is getting some updates, mainly for gradle config cache, so add an issue I guess?