Replies not permitted in thread drafts

[Ally]

Not only is it a good idea to be able to reply in thread drafts for the sake of release (e.g. "first reply!") but it'll also come in handy for API testing.
Posting as a bug report since replies used to be permitted in thread drafts.
I was wrong. API testing it is.

 

[Geek]

Replies were never permitted in thread drafts. Additionally, you are uanble to move threads from thread drafts to a real product/service forum. You'll need to copy the content. Therefore the reply of trying to be first reply or whatever wouldn't matter.

 

[Ally]

Replies were never permitted in thread drafts. Additionally, you are uanble to move threads from thread drafts to a real product/service forum. You'll need to copy the content. Therefore the reply of trying to be first reply or whatever wouldn't matter.

In which case I'll make this a suggestion. It'd still be a good API testing area.

 

[Harry]

In regards to API testing, Justis came up with the great idea of an additional token type for development purposes. The Ultimate member could use it themselves for testing and we'd also allow it to be shared with developers they hire - preventing the need for the developer to have to purchase Ultimate themselves. Perhaps it also automatically refreshes after X days.

It would return dummy data for all endpoints and any attempted writes would return as if they succeeded, but not actually write anything to the database.

 

[Ally]

In regards to API testing, Justis came up with the great idea of an additional token type for development purposes. The Ultimate member could use it themselves for testing and we'd also allow it to be shared with developers they hire - preventing the need for the developer to have to purchase Ultimate themselves. Perhaps it also automatically refreshes after X days.

It would return dummy data for all endpoints and any attempted writes would return as if they succeeded, but not actually write anything to the database.

Brilliant idea; this would be pretty sustainable going forward for both server API and wrappers.
That'd be really really helpful for unit testing too .