Bitmessage/PyBitmessage-2024-11-30
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 53 Actions Packages Projects Releases 5 Wiki Activity

Mark inbox messages as read via API #368

Closed
DivineOmega wants to merge 1 commits from api_set_read_status into master
pull from: api_set_read_status
merge into: Bitmessage:master
Conversation 3 Commits 1 Files Changed 1 +15
DivineOmega commented 2013-08-03 00:06:46 +02:00 (Migrated from github.com)
Copy Link

A new 'setRead' method allows you to mark an inbox message as read via the API.

A new 'setRead' method allows you to mark an inbox message as read via the API.
Atheros1 commented 2013-09-03 06:22:34 +02:00 (Migrated from github.com)
Copy Link

I've added this functionality to getInboxMessageByID.

I've added this functionality to getInboxMessageByID.
ralyodio commented 2013-09-03 07:32:46 +02:00 (Migrated from github.com)
Copy Link

I just tried setting read state to 1 via getInboxMessageById(id, 1); and it doesn't seem to work when I call getAllInboxMessages. I don't see the messages state changing from 0 to 1.

I just tried setting read state to 1 via getInboxMessageById(id, 1); and it doesn't seem to work when I call getAllInboxMessages. I don't see the messages state changing from 0 to 1.
ralyodio commented 2013-09-03 07:38:55 +02:00 (Migrated from github.com)
Copy Link

nevermind, I had to send boolean (true/false) in javascript, Not 1 or 0.

nevermind, I had to send boolean (true/false) in javascript, Not 1 or 0.
This repo is archived. You cannot comment on pull requests.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something isn't working as it's supposed to

  
build

Related to building or build system

  
dependencies

Pull requests that update a dependency file

  
developers

The issue is relevant mainly for developers rather than users

  
documentation

   
duplicate

   
enhancement

New feature

  
formatting

Code or UI text formatting

  
invalid

   
legal

   
mobile

Frontend for mobile devices (kivy)

  
obsolete

   
packaging

   
performance

   
protocol

Protocol change

  
question

   
refactoring

   
regression

Some issue, fixed in the past, appears again

  
security

   
test

   
translation

   
usability

   
wontfix
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-11-30#368
No description provided.
Delete Branch "api_set_read_status"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?