Releases: onflow/flixkit-go
v1.2.1-cadence-v1-M1
Pre Release to be Cadence v1.0 compliant
FLIX Template Generation Changes
- Supports specific networks user passes in to
CreateTemplate
this removes the dependecies on testnet and mainnet. - Only uses core contracts that have deployments on user's networks
Full Changelog: v1.2.1-cadence-v1-M1...v1.2.1-cadence-v1-M1
v1.1.2
v1.1.1
version 1.1.0
What's Changed
Breaking Changes
Reorganizing the code is not backwards compatible with main functionality.
type FlixService interface {
// GetTemplate returns the raw flix template
GetTemplate(ctx context.Context, templateName string) (string, string, error)
// GetAndReplaceImports returns the raw flix template with cadence imports replaced
GetTemplateAndReplaceImports(ctx context.Context, templateName string, network string) (*FlowInteractionTemplateExecution, error)
// GenerateBinding returns the generated binding given the language
GetTemplateAndCreateBinding(ctx context.Context, templateName string, lang string, destFile string) (string, error)
// GenerateTemplate returns the generated raw template
CreateTemplate(ctx context.Context, contractInfos ContractInfos, code string, preFill string) (string, error)
}
Full Changelog: v1.0.2...v1.1.0
Version 1.0.2
When generating FLIX v1.1 template add Output property.
This gives better support for typescript binding file generation.
Version 1.0.1
Fix issue when inconsistent formatting of addresses for addresses in network dependencies in FLIX.
Version 1.0.0
Breaking change, new code structure
Support JavaScript and TypeScript binding file generation for FLIX v1.0 and v1.1 🌐
Support FLIX v1.1 template generation 🧑🍳
Support Cadence Doc pragma parsing for FLIX v1.1 generation 🤘
Support retrieving Network specific Cadence for FLIX v1.0 and v1.1 🕸️
Version 0.3.1
Fix issue where binding templates are not accessible when using NewFclJSGenerator
. Converted tmpl files to go files so they are included in flixkit-go binding sub module.
Version 0.3.0
📄🛠️ Support generating v1.0.0 FLIX json files! Given Cadence transaction or script code, use generator/flixkitv1_0_0
module to generate FLIX, pass in a pre-filled FLIX FlowInteractionTemplate object to add human readable Messages
metadata.
In a future release it will be possible to generate v1.1.0 FLIX and use Messages
metadata found directly in the Cadence code.
Version 0.2.0
🐹 + 🌐 Added new bindings
module that generates javascript binding file based on FLIX. The javascript binding file leverages fcl-js ability to consume a FLIX json file directly. Requirement is fcl-js version 1.3 or greater.
Now there is a clear handoff point between smart contract developers and web developers.