API call of asignees #196
Labels
No Label
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#196
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
"assignee": "string"
is deprecateduse
"assignees": [ "string" ]
instead-> use at creat issue and more?
@6543
assignee
is removed from the APIs?Which version of Gitea will have this in effect?
If you check the Issues model, it have both assignee and assignees.
https://gitea.com/gitnex/GitNex/src/branch/master/app/src/main/java/org/mian/gitnex/models/Issues.java
At most it will effect creating new issue because the assignee object is required.
It wont be removed - it's not recomend to use it ...
I rewrote the function who parse this ... gitea/#8873
And noticed that assignee is only for backwarts compatibilety ...
So:
assignees
onlyIt need to be implemented that way to not break the current flow for old versions as that PR is merged to 1.11 and assignee is required for old versions(even it should not as you mentioned).
But it is not really a required thing at this moment. If we don't implement it until 1.11 release, anything will break?
We can make it optional, but somehow we need to know the API accept it as optional not mandatory.
This is the important bit because Gitea until 1.10 make it mandatory if I am not mistaken.
I'll test it ... and make a PR