Skip to content

enable declaring custom topics for ffi interface publish and ff publish api create #140

Open
ka1ii wants to merge 2 commits into
release-v1.3.3from
custom-topics
Open

enable declaring custom topics for ffi interface publish and ff publish api create #140
ka1ii wants to merge 2 commits into
release-v1.3.3from
custom-topics

Conversation

@ka1ii

@ka1ii ka1ii commented Apr 1, 2026

Copy link
Copy Markdown

addresses this issue: hyperledger-firefly#1725

example of ff define interface and ff create contract api being on the same topic

image

Signed-off-by: Kaijun Zhang <kaijun1543111@gmail.com>
@ka1ii ka1ii requested a review from a team as a code owner April 1, 2026 19:34
@ka1ii ka1ii changed the title enable declaring custom topics for ffi define and ff api create enable declaring custom topics for ffi interface publish and ff publish api create Apr 1, 2026
Signed-off-by: Kaijun Zhang <kaijun1543111@gmail.com>

var filtered []string
for _, t := range customTopics {
if t != "" {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder if this filtering is needed, or if we should just let it go through and fail later (I assume message validation fails if you pass no topics or empty topics?)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea but then we would need to add a try catch + this allows us to detect if we need to use the default topic or use the ones declared by the client

},
QueryParams: []*ffapi.QueryParam{
{Name: "confirm", Description: coremsgs.APIConfirmMsgQueryParam, IsBool: true},
{Name: "topics", Description: coremsgs.APICustomTopicsQueryParam, IsArray: true},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably need to consider if this should be a query param or body param... I was expecting it to be in the body (like NetworkName)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought of topic as something about the request, but I think you are right here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants