feature: integrate publication contract with community & channel cont… #130
Conversation
src/publication/publication.cairo
Outdated
| jolt_type: JoltType::Tip, | ||
| recipient: profile_address, | ||
| memo: "Tip User", | ||
| amount: current_tip_amount + amount, |
There was a problem hiding this comment.
mentioned this earlier, but the amount should be just amount. there's no need to add anything here.
| > of IKarstPublications<ComponentState<TContractState>> { | ||
| // ************************************************************************* | ||
| // PUBLISHING FUNCTIONS | ||
| // ************************************************************************* | ||
| /// @notice performs post action | ||
| /// @param contentURI uri of the content to be posted | ||
| /// @param profile_address address of profile performing the post action | ||
| fn post(ref self: ComponentState<TContractState>, post_params: PostParams) -> u256 { | ||
| fn post(ref self: ComponentState<TContractState>, mut post_params: PostParams) -> u256 { | ||
| // Initialize approval flag as false |
There was a problem hiding this comment.
after a few more research, it will be easier for us to make pub id unique from the get go, tying it to the profile address is not the most scalable approach. Let's just have a publication counter and increase it anytime a post, comment, repost is made
src/publication/publication.cairo
Outdated
| ref self: ComponentState<TContractState>, | ||
| profile_address: ContractAddress, | ||
| pub_id: u256, | ||
| channel_id: u256, |
There was a problem hiding this comment.
you don't need to pass in the channel and community id, as these are already stored in the publication struct. retrieve the publication using the pub id and get the channel id and community id from there
| profile_address: ContractAddress, | ||
| pub_id: u256, | ||
| channel_id: u256, |
There was a problem hiding this comment.
get these ids from the publication struct
…ract